Information system for physicians

ABSTRACT

A computer system identifies supplemental materials most effective at increasing adherence for each of a plurality of different medications and provides the materials at an optimal point in time. An example method generates a first user interface for receiving an electronic prescription for a patient for a prescribed substance. Responsive to receiving the electronic prescription, the method includes obtaining adherence data for the patient, identifying supplemental programs associated with the prescribed substance from a database of supplemental programs, generating a second user interface that presents the supplemental programs for selection by the health care provider, and responsive to receiving selection of at least one of the supplemental programs in the second user interface, providing the supplemental programs to the patient. The supplemental programs identified from the database are associated with at least one rule relating to adherence data that is met by the adherence data for the patient.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. Non-provisional patentapplication Ser. No. 16/430,217, filed Jun. 3, 2019, which is acontinuation of U.S. Non-provisional patent application Ser. No.13/565,164, filed Aug. 2, 2012, which is a continuation-in-part of U.S.Non-provisional patent application Ser. No. 13/544,531, filed Jul. 9,2012, which in turn is a continuation-in-part of U.S. Non-provisionalpatent application Ser. No. 13/462,486, filed May 2, 2012, which in turnclaims the benefit of U.S. Provisional Application Ser. No. 61/635,613,filed Apr. 19, 2012, and U.S. Provisional Application Ser. No.61/611,942, filed Mar. 16, 2012, the entireties of which are herebyincorporated by reference.

FIELD OF THE INVENTION

The present invention relates generally to systems and methods forsupplementing patient and provider interactions, and specifically tosystems and methods for electronically enhancing patient and providerinteractions using supplemental programs in response to an electronicprescription request to increase patient adherence.

BACKGROUND OF THE INVENTION

Poor patient adherence is a major concern within the health careindustry. After visiting their health care provider and receiving atleast one prescription for substances, many patients fail to maintain alevel of dedication and adherence to their prescribed substances. Thisresults in increased costs to all parties involved in the health careindustry, including, but not limited to the patient, the health careprovider, the pharmacies, the pharmaceutical companies, and the healthinsurance companies. There are currently many methods used with the goalof increasing patient adherence, such as, the distribution of patienteducational material, coupons, and patient reminder services. However,there still remains a need for a system that can better utilize thesemethods to increase patient adherence.

One important element to increasing patient adherence is good healthcare provider-patient interaction. Because this interaction takes placeat the point-of-care while the patient is thinking about their currentphysical state, this interaction is crucial for facilitating patienthealth, awareness, and adherence. However, there is currently not asystem that allows for a health care provider to be fully aware ofwhether their patients are adhering to their prescriptions, while thepatients are at the point-of-care. Further, the current methods ofincreasing patient adherence through educational and financialincentives require the health care provider to not only know whether ornot their patients are adhering to their prescribed substances, but alsorequires the health care provider to have the specific educationmaterial and coupons/discounts for each patient's specific diagnoses andprescribed substances at the point-of-care. This is overly burdensomeand practically impossible for a health care provider who has patientswith a wide variety of health care needs. Therefore, there is also aneed for a system that can more easily and efficiently distributepatient educational materials, coupons, and other supplemental programsat the point-of-care.

Additionally, pharmaceutical companies are restricted in the number ofcoupons and other incentives they may distribute. Currently, the couponsand other incentives are distributed to patients without taking intoconsideration whether the patient receiving the coupon or otherincentive needs or will be incentivized by them. Therefore, there alsoremains a need for a system that can aid pharmaceutical companies indistributing coupons and other incentives to their customers in a moreefficient manner.

The systems and methods described herein help to fill the needs andsolve the issues described above.

According to one embodiment, the present invention is directed to amethod of provisioning a combined educational coupon, the methodcomprising: a) receiving, on a computer apparatus, electronicprescription data for a prescribed substance for a patient; b) thecomputer apparatus determining educational data relating to theprescribed substance and coupon data relating to the prescribedsubstance; and c) the computer apparatus generating a single data filecomprising the educational data relating to the prescribed substance andthe coupon data relating to the prescribed substance.

According to another embodiment, the present invention is directed to anon-transitory computer-readable storage medium encoded withinstructions which, when executed on a processor, perform a methodcomprising: a) receiving data relating to an electronic prescription ofa prescribed substance for a patient; b) searching one or more databasesfor educational data relating to the prescribed substance and coupondata relating to the prescribed substance; c) determining educationaldata relating to the prescribed substance and coupon data relating tothe prescribed substance; d) retrieving from the one or more databasesthe educational data relating to the prescribed substance and the coupondata relating to the prescribed substance; and e) generating a singledata file comprising the educational data relating to the prescribedsubstance and the coupon data relating to the prescribed substance.

According to yet another embodiment, the present invention is directedto a computer system for electronically generating educational couponsfor a prescribed substance, the computer system comprising: a processor;a storage device; a network interface; and instructions residing on thestorage unit, which when executed by the processor, causes the processorto: a) receive electronic prescription data for a prescribed substancefor a patient: b) determine educational data relating to the prescribedsubstance and coupon data relating to the prescribed substance; and c)generate a single data file comprising the educational data relating tothe prescribed substance and the coupon data relating to the prescribedsubstance.

According to another embodiment, the present invention is directed to amethod of supplementing an electronic prescription issued by a healthcare provider, the method comprising: a) receiving, on a computerapparatus, electronic prescription data generated by a health careprovider for a patient for a prescribed substance: b) the computerapparatus determining, from a plurality of available supplementalprograms stored on one or more databases, supplemental programs forwhich the patient is eligible based on the electronic prescription data;c) presenting to the health care provider, in a display device, a listof the eligible supplemental programs, each of the eligible supplementalprograms being selectable and de-selectable by the health care providerin the display device; and d) the computer apparatus activating eachsupplemental program from the plurality of available supplementalprograms that have been selected and confirmed by the health careprovider in the display device; and wherein one of the activatedsupplemental programs is a coupon service, and wherein step d) furthercomprises retrieving coupon data relating to the prescribed substancefrom the one or more databases, and provisioning a coupon based on thecoupon data to the patient; and wherein one of the activatedsupplemental programs is a prescribed substance education service, andwherein step d) further comprises retrieving education content relatingto the prescribed substance from the one or more databases, andtransmitting said education content to the patient, said coupon databeing integrated into the education content to create a combinededucational coupon.

According to another embodiment, the present invention is directed to amethod of providing educational materials to a patient, the methodcomprising: a) receiving, on a computer apparatus, electronicprescription data for a prescribed substance for a patient, saidelectronic prescription data including a diagnostic code; b) searchingone or more databases, using the computer apparatus, to determine: (1)general educational data relating to the prescribed substance andindependent of the diagnostic code; and (2) specific educational datarelating to the prescribed substance and based on the diagnostic code;and c) presenting to a health care provider, in a display device, a listof the general educational data and the specific educational datadetermined in step b) for provisioning to the patient.

According to another embodiment, the present invention is directed to anon-transitory computer-readable storage medium encoded withinstructions which, when executed on a processor, perform a methodcomprising: a) receiving electronic prescription data for a prescribedsubstance for a patient, said electronic prescription data including adiagnostic code; b) searching one or more databases to determine: (1)general educational data relating to the prescribed substanceindependent of the diagnostic code; and (2) specific educational datarelating to the prescribed substance based on the diagnostic code; andc) presenting to a health care provider, in a display device, a list ofthe general educational data and the specific educational datadetermined in step b) for provisioning to the patient.

According to yet another embodiment, the present invention is directedto a computer system for electronically generating coupons for aprescribed substance, the computer system comprising: a processor; astorage device; a network interface; and instructions residing on thestorage unit, which when executed by the processor, causes the processorto: a) receive electronic prescription data for a prescribed substancefor a patient, said electronic prescription data including a diagnosticcode; b) search one or more databases to determine: (1) generaleducational data relating to the prescribed substance independent of thediagnostic code; and (2) specific educational data relating to theprescribed substance based on the diagnostic code; and c) present to ahealth care provider, in a display device, a list of the generaleducational data and the specific educational data determined in step b)for provisioning to the patient.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention will become more fully understood from thedetailed description and the accompanying drawings, wherein:

FIG. 1 is a schematic diagram of a system for supplementing patient andprovider interactions to increase patient adherence according to oneembodiment of the present invention;

FIG. 2 is a schematic diagram of a health care provider system forsupplementing patient and provider interactions to increase patientadherence according to one embodiment of the present invention;

FIG. 3 is a schematic diagram of an electronic prescription system forsupplementing patient and provider interactions to increase patientadherence according to one embodiment of the present invention;

FIG. 4 is a schematic diagram of a supplemental program system forsupplementing patient and provider interactions to increase patientadherence according to one embodiment of the present invention;

FIG. 5 is a schematic diagram of a plurality of third party programvendors for supplementing patient and provider interactions to increasepatient adherence according to one embodiment of the present invention;

FIG. 6 is a schematic diagram of a pharmacy system for supplementingpatient and provider interactions to increase patient adherenceaccording to one embodiment of the present invention;

FIG. 7 is a schematic diagram of payor system for supplementing patientand provider interactions to increase patient adherence according to oneembodiment of the present invention;

FIGS. 8a-8c is a flow chart of a system for supplementing patient andprovider interactions to increase patient adherence according to oneembodiment of the present invention;

FIG. 9 is an illustration of a combined educational material and coupondocument according to one embodiment of the present invention;

FIGS. 10-15 are screen shots of graphical user interfaces used forsupplementing patient and provider interactions to increase patientadherence according to one embodiment of the present invention;

FIG. 16 is a flow diagram of a method of acquiring patient medicationhistory data according to an embodiment of the present invention;

FIGS. 17-28 are event diagrams of methods for supplementing patient andprovider interactions to increase patient adherence according toembodiments of the present invention;

FIG. 29 is a schematic diagram of a system for increasing patientadherence through the activation of supplemental programs according toone embodiment of the present invention;

FIG. 30 is a flow chart of a method for defining a plurality of cohortsof a program cohort group according to one embodiment of the presentinvention;

FIG. 31 is a schematic diagram depicting how the SP module defines aplurality of cohorts according to one embodiment of the presentinvention;

FIG. 32 is a schematic diagram of a method of defining a plurality ofdifferent permutations of eligible supplemental programs for a targetdrug according to one embodiment of the present invention;

FIG. 33 is a schematic diagram of a method of assigning a differentpermutation of eligible supplemental programs to each cohort out of aplurality of cohorts of a program cohort group according to oneembodiment of the present invention;

FIG. 34 is a schematic diagram of a cohort relation table according toone embodiment of the present invention;

FIGS. 35a-35b are a flow chart of a method for receiving data relatingto an electronic prescription for the target drug and activating thepermutation of supplemental programs associated with the health careprovider's cohort for the target drug according to one embodiment of thepresent invention;

FIG. 36a is a flow chart of a method of retrieving supplemental programdata in accordance with an alternate embodiment of the presentinvention;

FIG. 36b is a flow chart of a method of generating a document list ofall eligible supplemental programs that are selected and accepted by aprovider for an electronic prescription according to an alternateembodiment of the present invention;

FIG. 36c is a flow chart of a method of retrieving the documentassociated with supplemental programs that are selected and accepted bya provider for an electronic prescription according to an alternateembodiment of the present invention;

FIGS. 37a-37b are a flow chart of a method of parsing patient adherencedata into data grouping based on a plurality of different cohortsaccording to an embodiment of the present invention;

FIG. 38a is a graphical representation of the effectiveness of differentpermutations of supplemental programs on patient's first fill complianceaccording to one embodiment of the present invention; and

FIG. 38b is a graphical representation of the effectiveness of differentpermutations of supplemental programs on patient's medicationpersistency rate according to one embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

The following description of the preferred embodiment(s) is merelyexemplary in nature and is in no way intended to limit the invention,its application, or uses.

System Overview

Referring to FIG. 1, a schematic diagram of a system 1000 forsupplementing patient and provider interactions to increase patientadherence according to one embodiment of the present invention isillustrated. Generally, the system 1000 comprises a health care provider(HCP) system 100, an electronic prescription (EP) system 200, asupplemental program (SP) system 300, at least one third party programvendor 400, a pharmacy system 500, and a payor system 600 all inoperable communication with one another to form a wide area network(WAN).

As exemplified by FIG. 1, the components of the system 1000 are inoperable communication via the internet. However, the invention is notso limited and other electronic communication means may be utilized,such as a satellite network, a cellular network, a common carriernetwork(s), Wi-Fi, WiMAX or any combination thereof. Further, it shouldbe noted that operable communication includes any means of electroniccommunication, such as but not limited to wired and wireless electroniccommunication, in which data can be transmitted and received between thesystems and modules of the system 1000. Moreover, it should also benoted that operable communication includes both direct and indirectcommunication, as well as bi-directional communication between thesystems and modules of the system 1000.

As discussed in more detail below, the system 1000 of the presentinvention may be configured in other ways. Therefore, it should be notedthat the invention is not limited only to those configurationsexplicitly described herein and, in alternate embodiments the system1000 may take on other configurations and/or layouts. For instance, anyof the systems and/or modules of the system 1000 may be connected via alocal area network (LAN). For example, according to one embodiment ofthe present invention, the EP system 200 and the SP system 300 reside onthe same LAN, and therefore, may communicate via Ethernet and/or Wi-Fiover a LAN.

Referring to FIG. 2, a schematic diagram of an HCP system 100 accordingto one embodiment of the present invention is illustrated. The HCPsystem 100 comprises a server 110, a terminal 120, and a printer 130 inoperable communication. Further, as discussed in more detail below, theHCP system 100 may also be said to comprise at least one health careprovider 101. Although exemplified as comprising the above components,the HCP system 200 may comprise any number, more or less, of thecomponents listed above. For example, a particular HCP system 100 maycomprises a plurality of providers 101, a plurality of servers 110, aplurality of terminals 120, and/or a plurality of printers 130.

Generally, the HCP system 100 is an institution or organization thatprovides general and/or specific health care for those in need. Forexample, an HCP system 100 may be an entire hospital or health caresystem, a specialized practice group within a larger hospital or healthcare system, a private general practice, or a private specializedpractice. The health care provider 101 may be a medical doctor, a nursepractitioner, or a staff administrator who is authorized to issueprescriptions. As noted above, the HCP system 100 may comprise anynumber of providers 101, and a particular provider 101 may be associatedwith more than one HCP system 100 at any given time.

The server 110 of the HCP system 100 comprises a properly programmedprocessor (or central processing unit (CPU)) 111, a network interface112, and a memory device 113 all in operable communication. It should benoted the processor 111 may be considered the processor of the HCPsystem 100. Further, although exemplified as a single server 110, theinvention is not so limited and in alternate embodiments the HCP system100 may comprise any number of servers 110. Additionally, although notexemplified, it should be understood that the processor 111 can haveintegrated memory. The network interface 112 connects the server 110 tothe over systems and modules of the system 1000 via the internet. Theproperly programmed processor 111 of the HCP system 100 effectuates theperforming of the processes and functions described below, including butnot limited to, the storage of data to the memory 113 of the HCP system100, the performance of the processes and functions of a thin-clientportion of an electronic prescription (EP) module 203 and a supplementalprogram (SP) module widget 302, and the transfer (transmission andreceipt) of data from HCP system 100 to the other systems and modules ofthe system 1000.

In the exemplified embodiment, the memory 113 comprises the thin-clientportion of the EP module 203 and the SP module widget 302, both of whichare described in more detail below. Although exemplified as a singlememory unit, it should be noted that the memory 113 may comprise anynumber of databases used to store data, modules, or other information.For example, the memory may be used to store provider information,patient information, prescribed substance information, and appropriatesoftware to allow the provider 101 to interact with the thin-clientportion of the EP module 203 and the SP module widget 302.

Although exemplified as part of the memory 113, in other embodiments thethin-client portion of the EP module 203 may reside elsewhere on the HCPsystem 100 or on another system altogether. Further, in the exemplifiedembodiment the SP module widget 302 is integrated into the thin-clientportion of the EP module 203. However, it should be noted that theinvention is not so limited and in alternate embodiments, any portion ofthe SP module may be integrated into any portion of the EP module.Further, in one embodiment of the present invention, the SP module isnot integrated with the EP module, but is rather a completely separatemodule altogether.

The terminal 120 of the HCP system 100 may be a personal computer (PC)or a mobile electronic unit. Each terminal 120 of the HCP system 100comprises a properly programmed processor (not shown), a memory device(not shown), a power supply (not shown), a video card (not shown), adisplay device 121, firmware (not shown), software (not shown), anetwork interface (not shown) and a user input device 122 (e.g., akeyboard, mouse and/or touch screen). Although not exemplified, itshould be understood that the processor of the terminal 120 can haveintegrated memory. The properly programmed processor of the terminal 120is configured to effectuate the processes and functions described below,including, but not limited to the effectuation of the graphical userinterfaces (GUI) for display on the display device 121 of the terminal120 for the provider 101 and the transmission of user inputs from theprovider 101 via the input device 122 to the other systems and modulesof the system 1000.

As discussed in more detail below, after the provider 101 generates aprescription for a substance using the thin-client portion of the EPmodule 203, the electronic prescription is transmitted by the HCP system100 to the pharmacy system 500 for processing. Further, as alsodiscussed in more detail below, at any point during the prescriptionwriting processes using the EP module 203, the SP module widget 302 mayreceive electronic prescription data relating to the electronicprescription and transmits the electronic prescription data to the tothe SP system 300 for further processing.

Referring to FIG. 3, a schematic diagram of an EP system 200 accordingto one embodiment of the present invention is illustrated. Generally,the EP system 200 comprises a server 210 which comprises a properlyprogrammed processor (CPU) 211, a network interface 212, and a memoryunit 213 in operable communication. It should be noted that theprocessor 211 may be considered the processor of the EP system 200.Further, although exemplified as a single server 210, the invention isnot so limited and in alternate embodiments the EP system 200 maycomprise any number of servers 210. Additionally, although notexemplified, it should be understood that the processor 211 can haveintegrated memory. The network interface 212 connects the server 210 tothe over systems and modules of the system 1000 via the internet.

As discussed in more detail below, the processor 211 of the EP system200 effectuates the performance of the processes and functions describedherein, including but not limited to the performance of the processescarried out by the central portion of the EP module 202, the storage ofdata to the EP database 201, and the transfer of data between the EPsystem 200 and the other systems and modules of the system 1000.

The memory 213 of the EP system 200 comprises an electronic prescription(EP) database 201 and a central portion of the electronic prescription(EP) module 202. The EP database 201 stores information relating toelectronic prescriptions that are generated using and effectuated by theEP module, such as, but not limited to, provider data, patient data,prescribed substance data, payor data, and patient medication historydata. Further, although exemplified as a single memory unit, it shouldbe noted that the memory 213 may comprise any number of databases usedto store data, modules, or other information.

Generally, the EP module is one or more computer programs configured toallow a provider 101 to generate and transmit electronic prescriptionsto the pharmacy system 500. In embodiments where the EP module comprisesa central portion 202 and a client portion 203, the central portion 202is configured to do most of the heavy processing of the EP module.Further, in such embodiments, the client portion 203 is a thin-clientportion that does light processing and generates/displays userinterfaces for the provider 101 on the display device 121 of theirterminal 120.

As used herein, the central portion 202 and the thin-client portion 203of the EP module may be collectively defined as the “EP module.”Although exemplified as comprising a thin-client portion 203 thatresides within the memory 113 of the HCP system 100 and a centralportion 202 that resides within the memory 213 of the EP system 200, theEP module is not so limited. In alternate embodiments, the centralportion 202 of the EP module may reside elsewhere on the system 1000 orbe combined with the thin-client portion 203 of the EP module and resideon any of the systems of the system 1000. In embodiments where thecentral portion 202 and the thin-client portion 203 are combined, theprovider 101 may access the EP module via a web interface (portal) or anapplicant user interface using their terminal 120. One non-limitingexample of an EP module is Rcopia® by DrFirst®.

Referring to FIG. 4, a schematic diagram of a SP system 300 according toone embodiment of the present invention is illustrated. Generally, theSP system 300 comprises a server 310 which comprises a properlyprogrammed processor (CPU) 311, a network interface 312, and a memoryunit 313 in operable communication. It should be noted that the server310 may be considered the supplemental program server and the processor311 may be considered the processor of the SP system 300. Further,although exemplified as a single server 310, the invention is not solimited and alternate embodiments the SP system 300 may comprise anynumber of servers 310. Additionally, although not exemplified, it shouldbe understood that the processor 311 can have integrated memory. Thenetwork interface 312 connects the server 310 to the over systems andmodules of the system 1000 via the internet.

As discussed in more detail below, the processor 311 of the SP system300 effectuates the performance of the processes and functions describedherein, including but not limited to the performance of the processescarried out by the central portion 301 of a supplemental program (SP)module (e.g., the determination of eligibility performed by the SPmodule, the transfer of content to a patient or the HCP system 100, theenrollment of a patient into a service, etc.), the storage of data to asupplemental program database 303 and a record database 304, and thetransfer of data between the SP system 300 and the other systems andmodules of the system 1000.

The memory 313 of the SP system 300 comprises a central portion of theSP module 301, a supplemental program database 303, and a recordsdatabase 304. Although exemplified as a single memory unit, it should benoted that the memory 113 may comprise any number of databases used tostore data, modules, or other information. As used herein, the centralportion 301 and the widget 302 of the SP module may be collectivelydefined as the “SP module.”

Generally, the SP module is one or more computer programs configured todetermine, from a plurality of available supplemental programs, specificsupplemental programs for which a patient is eligible. Further, as alsodiscussed in more detail below, the SP module is configured to, amongother things: (1) receive electronic prescription data generated by aprovider 101 for a patient for a prescribed substance from either theHCP system 100, the EP module, or the EP system 200; (2) retrievepatient data, prescribed substance data, provider data, and/or payordata from one or more databases of the system 1000; (3) determine, froma plurality of available supplemental programs, specific supplementalprograms for which a patient is eligible; (4) determine delivery modesthat are available for each supplemental program in which the patient iseligible; (5) generate graphical user interfaces (GUIs) that aredisplayed to the provider 101 on the display device 121 of the HCPsystem 100; (6) receive inputs from the provider 101 via the inputdevice 122 of the HCP system 100; (7) generate an activation signal foreach supplemental program that is selected by the provider 101; (8)receive the activation signal from the HCP system 100; (9) activatesupplemental programs that are selected and confirmed by the provider101; (10) tailor content associated with an activated supplementalprogram for a specific delivery mode; and (11) deliver the contentassociated with the activated supplemental program to the patient.

As also discussed in more detail below, the central portion 301 of theSP module determines eligible supplemental programs, out of a pluralityof available supplemental programs, for a patient based on at leastelectronic prescription data and the rules of each availablesupplemental programs. Although not exemplified, the central portion 301of the SP module comprises a rules engine that determines theeligibility of each of the available supplemental programs for a patientbeing prescribed a particular substance. Further, the central portion301 of the SP module also comprises agents that reach out to the thirdparty content providers 400 to retrieve content relating to theplurality of supplemental programs. However, the invention is not solimited and in one embodiment, the central portion 301 of the SP moduledoes not comprise the rules engine, but rather just transmits at leastthe electronic prescription data to the third party content providers400, which in turn determines the eligibility of each of the availablesupplemental programs.

In the exemplified embodiments, the central portion 301 does most of theheavy processing of the SP module, while the SP widget 302 routes datato the central portion 301 and provides an interface for the provider101 to access the SP module. Although exemplified as comprising a SPmodule widget 302 that resides within the memory 113 of the HCP system100 (and more specifically, a SP module widget 302 that is integratedinto the EP module) and a central portion 301 that resides within thememory 313 of the SP system 300, the SP module is not so limited. Inalternate embodiments of the present invention, the central portion 301and/or the SP widget 302 may reside elsewhere on the system 1000, or thecentral portion 301 may be combined with the SP module widget 302 andthe combined SP module may reside on any system or module of the system1000. Further, as described herein, it should be understood that any ofthe processes or functions performed by either the central portion 301or the SP widget 302 may be performed partially or wholly by the otherportion of the SP module in an alternate embodiment of the presentinvention.

The supplemental program database 303 stores general supplementalprogram data, including, but not limited to the names of a plurality ofavailable supplemental programs, general information relating to each ofthe plurality of available supplemental programs, and the rules of eachof the available supplemental program. As discussed in more detailbelow, according to one embodiment of the present invention, asupplemental program is a document or service that is activated for apatient based on the defined rules of the supplemental program. Further,according to one embodiment of the present invention, each supplementalprogram is designed to increase the patient's adherence to a prescribedsubstance.

As also discussed in more detail below, the rules of each supplementalprogram dictate which patients are eligible for the supplementalprogram. Generally, each rule may be based on, among other things, asubstance currently being prescribed to the patient, the patient'smedical history, information relating to the provider, and/orinformation relating to the patient's payor or health insurance company.According to one embodiment of the present invention, the rules of thesupplemental programs are defined by a combination of an administratorof the SP system 300 and one or more pharmaceutical companies. However,the invention is not so limited, and in alternate embodiments the rulesmay be defined by any combination of the administrator of the SP system300, the pharmaceutical companies, and/or the third party programvendors 400.

It should be noted that although exemplified as residing entirely in thememory 313 of the SP system 300, in alternate embodiments, thesupplemental program database 303 may reside entirely on another systemof the system 1000 or be broken up and reside partially on two or moreof the systems of the system 1000. Specifically, in one alternateembodiment the supplemental program database 303 resides entirely on theHCP system 100, while in another alternate embodiment the supplementalprogram database 303 resides entirely on the EP system 200.

Further, as also discussed in more detail below, in one embodiment ofthe present invention the supplemental program database 303 may comprisethe underlying supplemental programs themselves. In such embodiments,the SP module does not have to reach out to the third party contentproviders 400 to retrieve content relating to a supplemental program orto enroll a patient in a supplemental program.

The record database 304 stores information relating to the parties andthe processes involved in supplementing an electronic prescription, suchas, but not limited to, patient data, prescribed substance data,provider data, payor data, and patient medication history data. Further,the record database 304 may further store provider preference data andpatient preference data. It should be noted that although exemplified asresiding entirely on the SP system 300, in alternate embodiments, therecord database 304 may reside entirely on another system of the system1000 or be broken up and reside partially on two or more of the systemsof the system 1000. Specifically, in one alternate embodiment the recorddatabase 304 resides entirely on the HCP system 100, while in anotheralternate embodiment the record database 304 resides entirely on the EPsystem 200.

Finally, according to one embodiment of the present invention, the SPsystem 300 further comprises an administrator. The administrator is anindividual (or group of individuals) who has access to the databases,modules, and engines of the SP system 300, and may configured todatabases, modules, and engines as they see fit. For example, in someembodiments of the present invention, the administrator may configurethe settings of the SP module (both central portion 301 and SP widget302), may configure the data stored in the one or more databases of theSP system 300, may configure the rules of the available supplementalprograms, and/or may configure the rules engine of the SP module.Therefore, the administrator of the SP system 300 has the ability toaccess and control the processes and functions of all of the componentsof the SP system 300.

Referring to FIG. 5, a schematic diagram of a plurality of third partycontent providers 400 according to one embodiment of the presentinvention is illustrated. Generally, the present invention is notlimited to any specific number of third party content providers 400.Therefore, although four third party content providers (410, 420, 430,440) are illustrated in FIG. 5, the present invention may comprise moreor less than four third party content providers 400. For example, in analternate embodiment of the present invention, one or more of the thirdparty content providers 400 may be combined.

Each third party content provider 400 comprises a server 410, 420, 430,440 which comprises a properly programmed processor (CPU) 411, 421, 431,441, a network interface 412, 422, 432, 442, and a memory unit 413, 423,433, 443 in operable communication. Although each third party contentprovider 400 is exemplified as comprising a single server 410 (or 420,430, 440), the invention is not so limited and in alternate embodimentsany of the third party content provider 400 may comprise any number ofservers. Additionally, although not exemplified, it should be understoodthat the processors 411, 421, 431, 441 can have integrated memory.Finally, the network interfaces 412, 422, 432, 442 connects theirrespective server 410, 420, 430, 440 to the over systems and modules ofthe system 1000 via the Internet.

As discussed in more detail below, the processors 411, 421, 431, 441 ofeach third party content providers 400 effectuates the performance ofthe processes and functions described herein, including but not limitedto the storage of data to the databases 401, 402, 403, and 404, thetransfer of content to a patient, the enrollment of a patient into aservice, and the transfer of data between each third party contentproviders 400 and the other systems (specifically the SP system 300) ofthe system 1000.

The memory unit 413 comprises a coupon database 401, the memory unit 423comprises an educational information database 402, the memory unit 433comprises a patient/medication reminder service database 403, and thememory unit 443 comprises a patient adherence service database 404.Although exemplified as a single memory unit, it should be noted thatany of the memory units 413, 423, 433, 443 may comprise any number ofdatabases used to store data, modules, or other information.

The coupon database 401 stores supplemental program coupon data relatingto a plurality of different coupon documents and coupon services for aplurality of substances that may be prescribed to a patient. Thesupplemental program coupon data may include the amount of a coupon, therules relating to the eligibility of a coupon or a coupon service, thedelivery modes of the coupon or coupon service, and other informationrelating to a particular coupon or coupon service. Further, it should benoted that a coupon may be, but is not limited to, a discount forprescribed substances, a rebate for prescribed substances, or a voucherfor a free trial of prescribed substances.

The educational information database 402 stores supplemental programeducational data relating to a plurality of different educationaldocuments for a plurality of different substances and diseases statesfor which a patient may be prescribed or diagnosed. The supplementalprogram educational data may include general educational documentsrelating to a plurality of different substances or disease states,specific educational documents relating to a plurality of differentsubstances or disease states, general educational services that relateto a plurality of different substances or disease states, specificeducational services that relate to a plurality of different substancesor disease states, and the rules relating to the eligibility of thedocuments and services listed above.

The patient/medication reminder service database 403 stores supplementalprogram reminder data relating to a plurality of different patientreminder services and substance (or medication) reminder services. Thesupplemental program reminder data may include information relating toappointment reminder services for a patient, prescription fillingreminder services for a patient, refill reminder services for a patient,and the rides relating to the eligibility of the services listed above.

The patient adherence service database 404 stores supplemental programadherence data relating to a plurality of adherence services forpatients. The supplemental program adherence data may includeinformation relating to a variety of different adherence programs andservices for patients, including the rules relating to the eligibilityof the services.

Referring to FIG. 6, a schematic diagram of a pharmacy system 500according to one embodiment of the present invention is illustrated. Inthe exemplified embodiment, the pharmacy system 500 comprises aprescription routing sub-system 501 and at least one prescriptionfilling sub-system 502, all in operable communication with one another.Generally, the prescription routing sub-system 501 is configured toelectronically receive a prescription for a substance from the HCPsystem 100 or the EP system 200 and route the prescription to aprescription filling sub-system 502.

The prescription routing sub-system 501 comprises a server 510 thatcomprises a properly programmed processor 511, a network interface 512,and a memory device 513 in operable communication. Although notexemplified, each of the prescription filling sub-systems 502 comprisesa properly programmed processor, a network interface, and a memory unit.Although exemplified as a single server 510, the invention is not solimited and in alternate embodiments the prescription routing sub-system501 may comprise any number of servers 510. Additionally, although notexemplified, it should be understood that the processor 511 can haveintegrated memory. The network interface 512 connects the server 510 tothe over systems and modules of the system 1000 via the internet. Theprocessor 511 of the pharmacy system 500 effectuates the processes andfunctions described herein, including but not limited to, the receptionof prescription data from the EP module, the transfer of prescriptionhistory information to the SP module, and the transfer of data betweenthe pharmacy system 500 and the other systems and modules of the system1000.

In the exemplified embodiment, the memory 513 of the prescriptionrouting sub-system 501 comprises a prescription filling system database504 and a patient prescription history database 505. The prescriptionfilling system database 504 stores the names, addresses and otherinformation relating to each of the prescription filling sub-system(s)502. The patient prescription history database 505 stores informationrelating to previous prescriptions routed by the pharmacy system 500 forpatients.

The prescription filling sub-system 502 is a system that fills theprescribed substance for an end user. For example, prescription fillingsub-system 502 may be a local pharmacy used by a patient.

Referring to FIG. 7, a schematic diagram of a payor system 600 accordingto one embodiment of the present invention is illustrated. Generally,the payor system 600 comprises a server 610 which comprises a properlyprogrammed processor (CPU) 611, a network interface 612, and a memoryunit 613 in operable communication. It should be noted that theprocessor 611 may be considered the processor of the payor system 600.Further, although exemplified as a single server 610, the invention isnot so limited and in alternate embodiments the payor system 600 maycomprise any number of servers 610. Additionally, although notexemplified, it should be understood that the processor 611 can haveintegrated memory. The network interface 612 connects the server 610 tothe over systems and modules of the system 1000 via the internet.

As discussed in more detail below, the processor 611 of the payor system600 effectuates the performance of the processes and functions describedherein, including but not limited to the storage of data to the database601 of the memory 613 and the transfer of data (e.g., patient insuranceinformation) between the payor system 600 and the other systems andmodules of the system 1000.

The memory 613 of the payor system 600 comprises a patient insurancedatabase 601. The patient insurance database 601 stores informationrelating to the payor of prescriptions for substances of patients, suchas, but not limited to, the patient's insurance company, the patient'sco-pay amount, and the patient's other deductibles. Further, althoughexemplified as a single memory unit, it should be noted that the memory613 may comprise any number of databases used to store data, modules, orother information.

Therefore, it may be said that the system 1000 comprises a plurality ofdatabases or one or more databases. Specifically, as noted above, thesystem 1000 comprises the EP database 201 on the EP system 200, thesupplemental program database 303 and the records database 304 on the SPsystem 300, the coupon database 401, the educational informationdatabase 402, the patient medication/reminder service database 403, andthe patient adherence service database 404 of the third party contentproviders 400, the prescription filling sub-system database 504 and thepatient prescription history database 505 of the pharmacy system 500,and the patient insurance database 601 of the payor system 600.

Supplemental Programs

A supplemental program, as used herein, may be any document that isprovided to a patient or any service in which a patient is enrolled thatis designed for increasing patient adherence to a prescribed substance.Stated another way, a supplemental program may be a document or servicedesigned to help patients understand their medication regimen and complywith it. For example, a supplemental program may be a coupon (or acoupon service) that is provided to a patient for a particularprescribed substance, educational material (either general or specific)that is provided to a patient for a particular prescribed substance ordisease state, a combined coupon/educational document (referred toherein as an “EduSAVE™” document, one example of which is exemplified inFIG. 9), a loyalty card, a prescription reminder service, an appointmentreminder service, a health care coaching service, or any other patientadherence service or document. In one embodiment, the availablesupplemental programs are all patient adherence programs. However, theinvention is not so limited and in alternate embodiments, some or all ofthe available supplemental programs may not relate to patient adherence.

As discussed in more detail below, eligibility of a supplemental programis determined by comparing one or more of a plurality of different dataelements (such as, but not limited to, a patient's general information,a patient's medical history, a brand name or formula of a substanceprescribed to a patient, other information relating to a substanceprescribed to a patient, a patient's payor's information (e.g., apatient's health insurance company and/or health insurance plan), aprovider's general or specific information) with the rules of each ofthe available supplemental programs. If the data element(s) meets therules for a specific supplemental program, then the patient isdetermined to be “eligible” for that program. For example, a specificprogram may only be eligible to patients who are being prescribed aparticular substance, patients who reside within a particular geographicregion, patients who have a specific history with a particularsubstance, patients who have at least specific co-pay for a particularsubstance, or patients whose providers meet certain qualifications.

As discussed in detail below, the determination of eligibility isdetermined by the SP module, and more specifically, by the rules engineof the SP module. Generally, the SP module receives and/or retrieves aplurality of data relating to the patient, the prescribed substance, theprovider, and/or the payor, and applies that data to the rules of eachof the available supplemental programs to determine supplementalprograms in which the patient is eligible.

Method for Supplementing Patient and Provider Interactions

Generally and in accordance with one embodiment of the presentinvention, a method for supplementing patient and provider interactionsto increase patient adherence generally comprises three steps: (1)determining, from a plurality of available supplemental programs,supplemental programs for which a particular patient receiving aprescription for a particular substance is eligible; (2) receivingconfirmation/approval from the patient's health care provider that theeligible supplemental program should be activated; and (3) activatingthe eligible supplemental programs that the provider hasconfirmed/approved in order to increase patient adherence to theprescribed substance.

1. Determining Eligible Supplemental Programs for a Patient

Referring to FIGS. 8a -8 c, a flow chart of a system for supplementingpatient and provider interactions to increase patient adherenceaccording to one embodiment of the present invention is illustrated.

According to one embodiment of the present invention, the process beginswhen a patient visits their health care provider 101 seeking health careadvice, and the provider 101, after diagnosing the patient, decides towrite an electronic prescription for a particular substance for thepatient. The electronic prescription is typically generated by theprovider 101 using the EP module. Specifically, in one embodiment of thepresent invention, the provider 101 drafts an electronic prescriptionusing the thin-client portion of the EP module 203, which resides on theHCP system 100.

Referring to FIG. 10, a screen shot of a graphical user interface (GUI)generated by the EP module (and specifically the thin-client portion 203of the EP module) to allow the provider 101 to generate an electronicprescription for a patient according to one embodiment of the presentinvention is illustrated. As shown in FIG. 10, the GUI comprisesinformation relating to the provider (at least their name) 1001,information relating to the patient 1002, information relating to thepharmacy 1003 where the electronic prescription will be transmitted,information relating to the formulary of the patient 1004, informationrelating to the patient's medical history 1005, and information relatingto a substance 1006 to be prescribed to the patient. Moreover, the GUIis not so limited and may further comprise information relating to theother medications previously prescribed to the patient, currentallergies or adverse reactions of the patient, or other previouslyrecorded problems of the patient.

Referring to FIGS. 11-14, multiple, sequential graphical user interfaces(GUIs) 1011, 1012, 1013, 1014 generated by the EP module to allow theprovider 101 to generate an electronic prescription for a patientaccording to one embodiment of the present invention are illustrated. Inthe GUI 1011 exemplified in FIG. 11, the provider 101 may select amedication for prescription. As shown, the provider 101 may search for anew substance to prescribe by name or may choose a substance from apre-established list of favorites. As shown in the GUI 1012 of FIG. 12,after a provider 101 chooses a substance to prescribe to the patient,the EP module generates and displays the GUI 1012, which comprises druginteraction warnings, formulary alerts based on the patient's formularystatus, and other medication alerts and warnings.

After the provider 101 confirms the substance in the GUI 1012, the EPmodule generates and displays GUI 1013 (shown in FIG. 13), which allowsthe provider to enter the details of the substance to be prescribed1006. For example, substance details such as the names, dosage,strength, form, duration, quantity, and refills are displayed forprovider 101 input, along with directions to the patient and/orpharmacist and other details relating to the filling pharmacy andprovider 101. After the provider 101, has entered all the requiredinformation using the input device 122 of their terminal 120 of the HCPsystem 100, the EP module generates a displays GUI 1014. As exemplifiedin FIG. 14, the GUI 1014 provides a summary of the electronicprescription for the substance for the provider's review. After theprovider 101 reviews and confirms that the prescription is accurate, theelectronic prescription for the substance is created.

Still also referring to FIGS. 8a -8 c, in the exemplified embodiment,after an electronic prescription for the substance is created by theprovider 101, the SP widget 302 retrieves data relating to theelectronic prescription from the thin-client portion of the EP module203. The SP widget 302 then transmits the electronic prescription datato the central portion 301 of the SP module residing on the SP system300, such that the central portion 301 of the SP module receives theelectronic prescription data, thereby completing step 801 in FIG. 8a .The electronic prescription data comprises first patient data that isspecific to the patient, first prescribed substance data that isspecific to the prescribed substance, first provider data that isspecific to the provider 101, and first payor data that is specific tothe payor.

The first patient data comprises the information that is part of theprescription and relates to the patient, such as but not limited to, thepatient's name, gender, date of birth (DOB), contact information(telephone and address), and the patient's formulary status.

The first prescribed substance data comprises information that is partof the prescription and relates to the prescribed substance, such as butnot limited to, the name of the prescribed substance, the dosage,strength, form, duration, and quantity of the prescribed substance, andthe number of refills listed on the prescription.

The first provider data comprises information that is part of theprescription and relates to the provider 101, such as but not limitedto, the provider's name, the address and phone number of the provider'spractice, and national provider identifier (NPI) number.

The first payor data comprises information that is part of theprescription and relates to the payor of the patient, such as but notlimited to, the payor's name and the formulary status (or health careplan) of the patient.

However, the invention is not so limited, and in an alternate embodimentof the present invention, the electronic prescription data may notrelate to an electronic prescription currently being prescribed by theprovider 101 for the patient, but rather relate to a refill, a renewal,or a previously prescribed substance. In such embodiments, theelectronic prescription data may be received by the SP module from oneof the other databases of the system 1000 (e.g., the EP database 201,the records database 304, the patient prescription history database 505,etc.).

Once the central portion 301 of the SP module receives the electronicprescription data, the central portion 301 of the SP module retrievesadditional data prior to determining supplemental programs for which thepatient is eligible. However, it should be noted that the invention isnot so limited and in alternate embodiments, the central portion 301 ofthe SP module may only retrieve a portion of the data listed herein ormay not retrieve any additional data prior to determining supplementalprograms for which the patient is eligible.

In the exemplified embodiment, the central portion 301 of the SP moduleretrieves patient data that is specific to the patient from the recorddatabase 304, thereby completing step 802. The retrieved patient datamay be referred to as “additional” or “second” patient data, or simplypatient data. The patient data comprises one or more of the patient'scurrent medication, the patient's recent drug fills, the patient's drugfill history, the patient's demographics, the patient's health care planor payor information, the patient's adherence information, and thepatient's clinical trial cohort (if the patient is part of a clinicaltrial cohort). The patient adherence information may relate to thepatient's past adherence to prescriptions for the same prescribedsubstance, for prescriptions to prescribed substances for the samedisease state, and/or the patient's general adherence to any combinationof the substances they have previously been prescribed to the patient.It should be noted that this information is in addition to the firstpatient data that was retrieved by the centralized portion of the SPmodule 301 from the created electronic prescription.

Further, the central portion 301 of the SP module may also retrieveprescribed substance data relating to the substance prescribed by theelectronic prescription from the record database 304, thereby completingstep 803. The retrieved prescribed substance data may be referred to as“additional” or “second” prescribed substance data, or simply prescribedsubstance data. The prescribed substance data comprises one or more ofthe prescribed substance's drug properties, the prescribed substance'stherapeutic class(es), a prescribed substance substitution code, theprescribed substance's formulary data, and a prescription indicator. Itshould be noted that this information is in addition to the firstprescribed substance data that was retrieved by the central portion 301of the SP module from the created electronic prescription.

The central portion 301 of the SP module may also retrieve provider datarelating to the health care provider 101 from the record database 304,thereby completing step 804. The retrieved provider data may be referredto as “additional” or “second” provider data, or simply provider data.The provider data comprises one or more of the provider's geographiclocation, the provider's state of residency, and the specialty of theprovider 101. It should be noted that this information is in addition tothe first provider data that was retrieved by the central portion 301 ofthe SP module from the created electronic prescription.

The central portion 301 of the SP module may also retrieve payor datarelating to the payor (e.g., a health care insurance company) of thepatient from the record database 304, thereby completing step 805. Theretrieved payor data may be referred to as “additional” or “second”payor data, or simply payor data. Further, according to one embodiment,if the record database 304 does not have any of the patient's payorinformation stored therein (or even if it does), then the centralportion 301 of the SP module may transmit a request to the payor system600 and receive back the patient's payor information from the patientinsurance database 601. The payor data comprises one or more of theformulary status (or health care plan) of the patient, the co-pay of thepatient, and any other information relating to the payor of the patient.It should be noted that this information is in addition to the firstpayor data that was retrieved by the central portion 301 of the SPmodule from the created electronic prescription.

According to one embodiment of the present invention, the centralportion 301 of the SP module first attempts to retrieve the relevantdata from the records database 304. Thereafter, if the records database304 does not comprise the relevant data required by the central portion301 to determine the eligible supplemental programs, then the centralportion 301 reaches out to at least one other database on the system1000, such as, but not limited to the EP database 201 and the patientinsurance database 601. In one embodiment, upon retrieving the relevantdata from one of the other databases of the system 1000, the centralportion 301 stores the relevant data in the records database 304 forfuture processing.

After the central portion 301 of the SP module retrieves the additionaldata required, the central portion 301, using the rules engine,determines, from a plurality of available supplemental programs,supplemental programs for which the patient is eligible based on theelectronic prescription for the substance. As discussed above, aplurality of available supplemental programs are stored within one ormore databases, which includes but is not limited to the supplementalprogram database 303 and the databases 401, 402, 403, 404 of the thirdparty content providers 400. As noted above, according to one embodimentof the present invention each available supplemental program is adocument that is provided to a patient or a service in which a patientis enrolled. Moreover, according to one embodiment, each availablesupplemental program is designed to increase patient adherence to theprescribed substance.

As also noted above, each supplemental program out of the plurality ofavailable supplemental programs comprises one or more rules. Generally,the rules of a supplemental program must be met in order for the patientto be “eligible” for the supplemental program. The rules may relate toinformation relating to the patient, the prescribed substance, theprovider, and/or the payor of the patient. Therefore, the rules of eachof the available supplemental programs may act as constraints and/orrestrictions dictating the eligibility of a patient for a particularavailable supplemental program.

Examples of rules include, but are not limited to, restricting asupplemental program to a specific prescribed substance or diseasestate, restricting a supplemental program to a specific prescribedsubstance of a specific dosage strength, restricting a supplementalprogram to patients or providers of a specific geographic region,restricting a supplemental program to patients who have a certainadherence history (whether with the prescribed substance or in general),restricting a supplemental program to patients who have a specificpersistency rate for the prescribed substance (e.g., a persistency rateunder 60%, a persistency rate between 30%-60%, or a persistency ratebetween 10%-85%), restricting a supplemental program to patients of acertain age or age range, restricting a supplemental program to patientswho have been prescribed the substance for at least a predetermined timeperiod, restricting a supplemental program to patients who have acertain co-pay for a specific prescribed substance, restricting asupplemental program to patient's having a certain health insurancecarrier, etc.

Therefore, for example, a specific supplemental program is only eligibleto patients who meet the rules described above. Restricting thedissemination of supplemental programs on the basis of the rules listedabove may be beneficial since supplemental programs will only go tothose patients with which they will have the greatest effect. Therefore,for example, a pharmaceutical company is not blindly handing out couponsto patients whose habits may not be affected by the receipt of a coupon.Rather, the coupons are distributed on the basis of predetermined rulesto increase the likelihood that the coupons will result in increasedadherence by the patient, and in turn, sales of the prescribed substanceand reduced costs to the other parties involved. Further, since thedetermination of eligibility is performed by the rules engine of the SPmodule, the health care provider 101, may, but is not required tocalculate or analyze whether a patient would be incentivized by asupplemental program. This helps to alleviate some of the burdentypically placed on health care providers 101 with regards todisseminating documentation to their patients.

Further, according to another embodiment of the present invention, rulesmay further include a patient's specific usage stage for a substance.Therefore, in one embodiment, a patient may only be eligible forsupplemental program that provides a specific coupon if they are at aspecific usage stage for a particular substance. For example, a patientmay only be eligible for a coupon if they are after their second refillfor a particular substance, or if they are between their third andfourth refill of a particular substance. In such embodiments, providingcoupons to a patient based on their specific usage stage for a substancemay encourage continued patient adherence for that substance.

The rules engine of the central portion 301 of the SP module determinesthe eligibility of each of the plurality of available supplementalprograms for the patient by comparing the data received/retrieved by theSP module with the rules of each available supplemental program. Asnoted above, the data used in the comparison includes, but is notlimited to, the first patient data received from the electronicprescription, the first prescribed substance data from the electronicprescription, the first provider data from the electronic prescription,the first payor data from the electronic prescription, the patient dataretrieved by the central portion 301 of the SP module, the prescribedsubstance data retrieved by the central portion 301 of the SP module,the provider data retrieved by the central portion 301 of the SP module,and the payor data retrieved by the central portion 301 of the SPmodule. Therefore, the eligibility of each of the available supplementalprograms is determined by the rules engine of the central portion 301 ofthe SP module using any combination of the data (or data elements)listed above.

Still referring to FIG. 8a , in decision step 806, the central portion301 of the SP module, using the rules engine, determines the eligibilityof the plurality of available supplemental programs by comparing thedata received and retrieved (e.g., the patient data, the prescribedsubstance data, the provider data, and the payor data discussed above)with the rules of each of the available supplemental programs. If thereceived/retrieved data does not meet the rules of any of the pluralityof available supplemental programs, then the process ends at step 807.However, if the received/retrieved data meets the rules of at least oneavailable supplemental program, then the process continues to step 808.It should be noted that those supplemental programs whose rules aredetermined by the rules engine to meet the received and retrieved dataare considered eligible supplemental programs.

Further, it should be noted that although exemplified as a singledetermination step, the invention is not so limited. In one embodimentof the present invention, the determination of eligible supplementalprograms by the rules engine of the SP module is a multi-step comparisonprocess. For example, in one embodiment of the present invention, duringa first comparison step the central portion 301 of the SP modulecompares the prescribed substance data (including either the firstprescribed substance data retrieved from the electronic prescriptionand/or the prescribed substance data retrieved from the record database304) with the rules of each of the available supplemental programs. Morespecifically, the rules engine of the SP module may compare the brandname or formula of the prescribed substance with each of the pluralityof available supplemental programs. If the brand name or formula of theprescribed substance matches the brand name or formula of a rule anavailable supplemental program, then that supplemental program passesthe first comparison step of the rules engine.

If the prescribed substance data does meet the rules of at least oneavailable supplemental program, then the central portion 301 of the SPmodule performs a second comparison step, whereby the SP module comparesthe patient data (including either the first patient data retrieved fromthe electronic prescription and/or the patient data retrieved from therecord database 304) with the rules of each of the supplemental programsthat passed the first comparison step. Thereafter, the SP module mayperform subsequent comparison steps using the provider data and/or thepayor data. In such embodiments, a patient is “eligible” for asupplemental program, if and only if, the supplemental program passeseach step of the multi-step comparison process.

It should be noted that in such multi-step comparison embodiments, theinvention is not limited to any specific number of comparison steps, theorder of the comparison steps, or the types of comparison steps (e.g.,steps using prescribed substance data, using patient data, usingprovider data, or using payor data).

Further, it should be noted that in an alternate embodiment of thepresent invention, the central portion 301 of the SP module transmitsthe data received and retrieved from the one or more databases (e.g.,the patient, prescribed substance, provider, and payor data discussedabove) to a third party system (e.g., one of the third party contentproviders 400). Thereafter, the third party system compares the dataagainst the rules of each of the available supplemental programs todetermine eligibility. After testing the data against the rules, thethird party system transmits a signal back to the central portion 301 ofthe SP module indicating which of the available supplemental programsare eligible. Therefore, in such embodiments, the SP module determinesthe eligibility of the available supplemental programs by transmittingthe appropriate data to a third party system and receiving back a signalindicating for which of the available supplemental programs the patientis eligible.

Although not exemplified, in one embodiment of the present invention,prior to performing step 806, the central portion 301 of the SP moduleretrieves provider preference data (and/or patient preference data) fromthe records database 304 and/or the supplemental program database 303.Provider preference data is information that relates to the preferencesof the specific provider 101 who drafted the prescribed substance.Similarly, patient preference data is information that relates to thepreferences of the patient which whom the substance is being prescribed.The preference data includes, but is not limited to, specific modes ofdelivery (e.g., print, email, SMS, etc.) and supplemental program types(e.g. educational material, coupons, reminder services, etc.) that theprovider 101 and/or patient prefers.

If the SP module locates and retrieves preferences for the provider 101and/or patient, then the following steps are limited to thosesupplemental programs and delivery modes that are preferred by theprovider and/or patient. For example, if the provider 101 sets theirpreferences to select only a specific type of supplemental program(e.g., educational material), then the SP module will only determineeligible supplemental programs that are of that specific type ofsupplemental program. For purposes of this discussion, we will assumethat the SP module does not retrieve any provider or patient preferencedata.

According to one embodiment of the present invention, the SP modulereceives provider 101 and/or patient preference data directly from theprovider 101 via the input device 122 of the HCP system 100. However, itshould be noted that in other embodiments of the present invention, theSP module may learn the preferences of a provider 101 and/or a patientbased on one or more previous instances where the provider 101 and/orpatient used the SP module. Upon receiving or learning provider 101and/or patient preference data, the central portion 301 of the SP modulestores the preference data in the record database 304.

After the SP module determines which of the available supplementalprograms the patient is eligible, the central portion 301 of the SPmodule retrieves supplemental program data relating to each of theeligible supplemental programs from the supplemental program database303, thereby completing step 808. It should be noted that, according toone embodiment of the present invention, the supplemental program datais not the actual supplemental program itself, but rather informationrelating to each of the supplemental programs.

In the exemplified embodiment, the supplemental program data comprisesinformation about the eligible supplemental program, such as, but notlimited to, the name of the eligible supplemental program, the specifictype of document or service the eligible supplemental program comprises,and delivery mode data relating to the available delivery modes of eachof the eligible supplemental programs. Further, it should be noted thatif the received/retrieved data meets the rules of more than oneavailable supplemental program, then the central portion 301 of the SPmodule retrieves supplemental program data relating to each of theplurality of eligible supplemental programs from the supplementalprogram database 303.

However, the invention is not so limited, and in another embodiment ofthe present invention, the central portion 301 of the SP moduleretrieves the supplemental program data from the one or more databases401, 402, 403, 404 of the appropriate third party content provider 400.Further, in another alternate embodiment, the central portion 301 of theSP module may receive the supplemental programs itself at step 808.

After retrieving the supplemental program data in step 808, the centralportion 310 of the SP module retrieves patient delivery mode datarelating to the delivery modes that are available for the patient fromthe record database 304 of the SP system 300, thereby completing step809. The patient delivery mode data comprises information relating tothe patient, such as but not limited to, an email address of thepatient, a phone number of the patient, and a mailing address of thepatient. It should be noted that the central portion 301 of the SPmodule can retrieve information about the patient that is currentlystored in the record database 304, along with patient data that isstored in the other, one or more databases of the system 1000.

After retrieving patient delivery mode data, the central portion 301 ofthe SP module compares the patient delivery mode data with the deliverymode data for each of the eligible supplemental programs, therebycompleting step 810. As noted above, the delivery mode data for theeligible supplemental programs is retrieved by the central portion 301in step 808. The comparison is done in order to determine qualifieddelivery modes for each of the eligible supplemental programs. Aqualified delivery mode is a delivery mode that is available for asupplemental program and a delivery mode in which the patient deliverymode data (e.g., the patient's email address, phone number, etc.)relating to that delivery mode is stored in the SP system 300 and hasbeen retrieved by the SP module.

As discussed in more detail below and according to one embodiment of thepresent invention, eligible supplemental programs that do have qualifieddelivery modes may be preselected by the SP module for those specificdelivery modes. Further, in another embodiment of the present invention,eligible supplemental programs that do not have at least one qualifieddelivery modes associated therewith may be locked so as to be incapableof selection by the provider 101. In such embodiments, if the provider101 may be required to enter patient delivery mode information into theGUI of FIG. 15 described below in order to unlock the selectionmechanism for that particular supplemental program. Further, it shouldbe noted that the invention is not so limited, and in other alternateembodiments the qualified delivery modes may just be preselected by theSP module, while the non-qualified delivery modes are grayed-out or onlyselectable upon the provider 101 entering the appropriate patientdelivery mode information.

Further, in yet another embodiment of the present invention, the SPmodule does not retrieve patient delivery mode data and, therefore acomparison between patient delivery mode data and delivery mode data foreach of the eligible supplemental programs is not performed by the SPmodule. In such instances, all of the available delivery modes for eachof the eligible supplemental programs may be displayed in the GUI to theprovider 101 using the display device 121.

2. Receiving Confirmation from the Health Care Provider to Activate theSupplemental Programs

After the SP module has determined supplemental programs for which thepatient is eligible, the SP module generates and displays a GUI to theprovider 101 in order to receive confirmation from the provider 101regarding which of the eligible supplemental programs should beactivated.

Referring to FIG. 8b and after step 810, the SP module generates a GUIthat comprises a list of the eligible supplemental programs for theprovider's selection and confirmation by the health care provider 101,thereby completing step 811. In one embodiment of the present invention,the central portion 301 of the SP module generates the GUI thatcomprises the list of eligible supplemental programs for the patient,and then transmits the GUI to the SP widget 302 for display to theprovider 101 in the display device 121. However, in alternateembodiments of the present invention, the GUI is generated and displayedby the SP widget 302.

After the GUI is generated, the SP widget 302 displays the GUI in thedisplay device 121 of the terminal 120 to the provider 101, therebycompleting step 812. One example of a GUI is shown in FIG. 15. Asexemplified by the GUI of FIG. 15, the GUI comprises a pop-up window1010, which comprises information relating to the substance 1011 forwhich eligible supplemental programs are being presented, informationrelating to the eligible supplemental programs 1012, selectionmechanisms 1013 for each of the eligible supplemental programs,information relating to delivery modes 1014 available for the eligiblesupplemental programs, delivery mode selection mechanisms 1015 for eachof the delivery modes available for each of the eligible supplementalprograms, delivery mode input fields 1016, a confirmation mechanism1017, and a cancellation mechanism 1018.

Still referring to FIG. 15, although only one substance is listed in thewindow 1010, it should be noted that section 1011 may compriseinformation relating to a plurality of prescribed substances. Forinstance, if the provider 101 drafts more than one prescription relatingto more than one substance for the patient and the SP module determinesthat there are eligible supplemental programs relating to more than oneof the prescribed substances, then the window 1010 will comprises a listof each of the substances 1011 along with a list of each of theirassociated eligible supplemental programs 1012.

As further exemplified by the window 1010; section 1012 which comprisesa list of the eligible supplemental programs for each of the prescribedsubstances, also comprises a selection mechanism 1013 to allow theprovider 101 to determine which of the eligible supplemental programsthey would like to activate for their patient. The selection mechanism1013 allows each of the eligible supplemental programs to be selectedand/or deselected by the provider 101 using the input means 122 of theHCP system 100. As discussed in more detail below, the eligiblesupplemental programs that are selected (e.g., via a check box) by theprovider 101 using the selection mechanism 1013 when the confirmationmechanism 1017 is actuated by the provider 101 will be activated by theSP module for the patient upon the provider 101 actuating theconfirmation mechanism 1017. Although exemplified as a check box, theinvention is not so limited and in alternate embodiments the selectionmechanism 1013 may be changed to include any selection mechanism knownin the art.

Moreover, as discussed above, it should be noted that if thesupplemental program database 303 and/or the records database 304comprises provider preference data and/or patient preference data, thenthe SP module will upload that information and generate the window 1010based on that information. For instance, if the preference data relatesto specific types of supplemental programs or delivery modes preferredby the provider 101 or patient, then the selection mechanisms 1013, 1015for those supplemental program and/or delivery modes will bepre-selected when the window 1010 is generated by the central portion301 of the SP module and displayed by the SP widget 302 on the displaydevice 121 for the provider 101.

Still referring to the window 1010 shown in FIG. 15, a list of availabledelivery modes 1014 for the eligible supplemental programs is alsodisplayed for the provider 101. As shown, each delivery mode comprises adelivery mode selection mechanism 1015 that may be selected and/ordeselected by the provider 101 using the input means 122. The deliverymode selection mechanisms 1015 allow the provider 101 to determine howthe supplemental programs will be delivered to the patient. Further, itshould be noted that more than one delivery mode may be selected by theprovider 101. In such instances, the supplemental programs will bedelivered to the patient via all of the selected delivery modes.Although the delivery modes are shown to comprise print, email, andtext/SMS, the invention is not so limited and in alternate embodiments,the delivery modes may also include mailing to the patient's address,along with other methods of delivering documents to the patient.

Further, the window 1010 also comprises the delivery mode input fields1016, which allow a provider 101 to manually enter in the patient'smobile phone number, email address, or other patient delivery modeinformation required for delivery of a supplemental program. If theprovider 101 enters patient delivery mode information into a deliverymode input field 1016, then upon the provider 101 actuating theconfirmation mechanism 1017, the SP module stores the patient's deliverymode information in one or more databases of the system 1000 (e.g., therecords database 304) for future instances. Additionally, it should benoted that if the patient's delivery mode information (e.g., email,phone number, address, etc.) is previously stored in one or more of thedatabases of the system 1000 (e.g., the record database 304, the EPdatabase 201, etc.), then the SP module will retrieve the patient'sdelivery mode information from the one or more databases andauto-populate the delivery mode input fields 1016 in window 1010.

Further, one of the delivery mode input Field 1016 shown in the window1010 is a preview field. The preview field allows the provider 101 topreview the eligible supplemental program(s) before activating theprogram(s) for the patient. If the supplemental program is a coupon,education material, or other document, then another window displayingthe document or information relating to the document will be generatedand displayed by the SP module in the display device 121. According toone embodiment of the present invention, if the supplemental program isa service, then another window displaying general information relatingto the service will be generated and displayed by the SP module in thedisplay device 121.

As noted above, according to one embodiment of the present invention,prior to generating and displaying the window 1010, the SP moduleretrieves delivery mode data relating to the eligible supplementalprogram and the patient. In the list of delivery modes 1014 exemplifiedin FIG. 15, “print” is a qualified delivery mode and the delivery modeinput field 1016 for print has been pre-selected by the SP widget 302.Since the other delivery modes, such as email and mobile, do notcomprise patient delivery mode data, they are not qualified deliverymodes and are not pre-selected by the SP module.

Referring to both FIG. 8b and FIG. 15, after the provider 101 hasselected the eligible supplemental programs and the delivery mode(s) forthe eligible supplemental programs that they would like to activate forthe patient, the provider 101 actuates the confirmation mechanism 1017.Upon actuating the confirmation mechanism 1017, the SP widget 302generates and transmits an activation signal for each of thesupplemental programs that have been selected by the provider 101 to thecentral portion 301 of the SP module, thereby completing step 813. Eachof the activation signals comprises information relating to the eligiblesupplemental program itself, along with the delivery mode selected bythe provider 101. However, the invention is not so limited and inalternate embodiments, the SP widget 302 generates and transmits asingle activation signal that comprises information relating to all ofthe eligible supplemental programs that were selected by the provider101.

Although exemplified as an icon in the window 1010, the confirmationmechanism 1017 is not so limited. In alternate embodiments, theconfirmation mechanism 1017 may be a button, switch, lever, etc. thatcan be actuated by the provider to confirm the selected eligiblesupplemental programs and delivery modes.

However, if the provider 101 decides that they do not want to have anyof the eligible supplemental programs activated for the patient, thenthe provider 101 may actuate the cancellation mechanism 1018. Uponactuating the cancellation mechanism 1018, the SP widget 302 generatesand transmits a cancellation signal to the central portion 301 of the SPmodule. In such instances, none of the eligible supplemental programsare activated for the patient.

As shown in FIG. 15, the window 1010 is displayed concurrently with theelectronic prescription interface that was used to generate theelectronic prescription data previously received by the SP module. Morespecifically, the window 1010 overlays the electronic prescriptioninterface and is automatically generated and displayed by the SP modulein the display device 121 during the electronic prescriptions sessionundertaken by the provider 101. By using such a system, the provider 101does not have to leave their electronic prescription writing interfacein order to be presented with eligible supplemental programs for theirpatients. Stated simply, the SP module, due in part to the SP widget 302being integrated into the EP module, provides one continuous interfacefor the provider 101 during their prescription writing/supplementalprogram activating process.

This is beneficial because it allows the provider 101 to know what sortsof supplemental programs are available for their patient and,specifically for the substance the provider 101 is currently prescribingfor their patient, without having to leave their electronic prescriptionwriting interface. Such a system encourages providers 101 to disseminatedocuments and enroll their patients in services to increase theirpatient adherence in their prescribed substances.

Further, additional benefits arise from granting the provider 101 theability not only to select what specific supplemental programs will beactivated for each and every one of their patients, but also the abilityto preview the supplemental programs before they are activated for thepatient. Additionally, the provider 101 may select the specific deliverymode for each patient. Therefore, the provider 101 may tailor thesupplemental programs depending on the particular preferences of thepatient, as well as what the provider 101 believes will result in themost beneficial results. Finally, allowing the provider 101 to be thegatekeeper between the supplemental programs and the patient encouragescommunication between the provider 101 and patient, which ultimatelyresults in better care for the patient.

Although exemplified as pop-up window 1010, it should be noted that theinvention is not so limited. In alternate embodiments, the providerinterface created by the SP module may be any interface designed toallow the provider 101 to select and confirm the specific supplementalprograms they would like to be delivered to the patient. For example,the interface may be a screen that takes up the entirety of the displaydevice 121 or a window that is separate from the EP module (as opposedto pop-up window 1010, which is displayed on top of the electronicprescription writing interface). Stated simply, the current invention isnot limited to the type of interface generated and displayed to theprovider 101.

3. Activating the Eligible Supplemental Programs that Have BeenConfirmed by the Health Care Provider

In general, activation of an eligible supplemental program begins whenthe provider 101 actuates the confirmation mechanism 1017 afterselecting the programs they would like to be activated for theirpatient. In the embodiments discussed with reference to FIGS. 8a -8 c,activation begins with step 813 and continues to step 818. However, itshould be noted that in alternate embodiments of the present invention,activation further includes step 819 and sometimes even step 820.Moreover, in another embodiment of the present invention, activationonly includes step 813, which comprises the SP widget 302 generating andtransmitting an activation signal to the central portion of the SPmodule 301 upon the provider 101 actuating the confirmation mechanism1017.

Referring to FIG. 8b , after the SP widget 302 generates and transmitsthe activation signal for each of the supplemental programs, the centralportion 301 of the SP module receives the activation signals, therebycompleting step 814. Using the received activation signals, the centralportion 301 of the SP module determines which of the eligiblesupplemental programs the provider 101 has confirmed.

Thereafter, the central portion 301 of the SP module transmits therelevant data for one of the confirmed supplemental program to theappropriate third party content provider 400, thereby completing step815. For instance, if the confirmed supplemental program is a document(e.g., a coupon, educational material, EduSAVE™, etc.), then the centralportion 301 of the SP module transmits at least a request for thedocument(s) to the appropriate third party content provider 400.Similarly, if the supplemental program is a service (e.g., aprescription reminder service, a medication reminder service, anappointment reminder service, a patient adherence service, etc.), thenthe central portion 301 of the SP module transmits a request for patientenrollment in the service. Therefore, depending on the specific documentor service requested, the central portion 301 of the SP module transmitsthe relevant request to the appropriate server 410, 420, 430, 440 of thethird party content provider 400.

It should be noted that in some embodiments of the present invention,the central portion 301 of the SP module may also transmit patientdelivery mode data to the third party content provider 400. This may berequired if the third party content provider 400 is to deliver thecontent directly to the patient or enroll the patient directly into theservice.

Upon receiving the request from the central portion 301 of the SPmodule, the appropriate third party content provider 400 determineswhether the request is for a document or a service. If the request isfor a document, then the third party content provider 400 generates thedocument and returns the document to the central portion 301 of the SPmodule. If the request is for a service, then the third party contentprovider 400 configures the service and transmits a configuration signalback to the central portion 301 of the SP module. Specifically, thecorresponding document or service is retrieved from the appropriate oneof the databases 401, 402, 403, 404.

Thereafter, the central portion 301 of the SP module receives thedocument(s) and/or enrollment confirmation signal from the third partycontent system 400, thereby completing step 816. Next, the centralportion 301 of the SP module determines if there are any other eligiblesupplemental programs for which a request has yet to be delivered to thethird party vendor system 400 at decision step 817. If there areadditional confirmed supplemental programs for which relevant data hasnot yet been transmitted to the third party content system 400, then theprocess returns to step 815 and the central portion 301 of the SP moduletransmits the relevant data for another of the confirmed supplementalprogram to the appropriate third party content provider 400. However, ifthe relevant data has been transmitted to the third party content system400 for each of the confirmed supplemental programs, then the processcontinues to step 819.

It should be noted that in one embodiment of the present invention, thecentral portion 301 of the SP module transmits the relevant data for allof the confirmed supplemental programs to the appropriate third partycontent provider 400 at step 815. In such instances, decision step 817may be omitted.

Therefore, after a request has been delivered by the central portion 301of the SP module to the appropriate third party content provide 400 forall of the eligible supplemental programs that were confirmed by theprovider 101, the SP module has activated each of the supplementalprograms. Generally, by activating a supplemental program the SP moduleeither receives content, such as a document to the patient, that is tobe delivered to the patient or enrolls the patient in one of theaforementioned services via the appropriate third party content provider400.

A non-limiting list of examples whereby the SP module activates asupplemental program is discussed below. It should be noted that theinvention is not limited to the explicit examples presented herein. Inone embodiment, in which the supplemental program is a coupon service,the SP module activates the supplemental program by retrieving coupondata relating to the prescribed substance from the coupon database 401of the appropriate third party content provider 400 and integrating thecoupon data into the electronic prescription. The integration of thecoupon data into the electronic prescription is done by the SP widget302, which is integrated into the thin-client portion 320 of the EPmodule residing on the HCP system 100. Thereafter, the HCP system 100may transmit the electronic prescription with integration coupon to thepharmacy system 500 for further processing.

In another embodiment, in which the supplemental program is a couponservice, the SP module activates the supplemental program by retrievingthe coupon data and provisioning a coupon based on the coupon data.Further, in one embodiment, activation further includes the SP moduledelivering the coupon to the patient via the selected delivery mode. Forinstance, the coupon may be delivered to the HCP system 100 so theprovider 101 may print the coupon out for the patient using the printer130, or the coupon may be delivered directly to the patient via one ofthe delivery modes discussed above.

For further example, in one embodiment in which the supplemental programis a prescribed substance education service, the SP module activates thesupplemental program by retrieving educational content relating to theprescribed substance from the educational information database 402 ofthe appropriate third party content provider 400. Thereafter, accordingto one embodiment, activation may further include the SP moduledelivering the education content to the patient via the selecteddelivery mode. Therefore, the education content may be delivered to thepatient by transmitting the educational content to the HCP system 100 sothe content may be printed by the provider 101 for the patient using theprinter 130, or the educational content may be delivered directly to thepatient via one of the delivery modes discussed above.

Additionally, in another embodiment in which the supplemental programsis a prescribed substance education service and/or a coupon service, theSP module activates the supplemental program by retrieving educationcontent relating to the prescribed substance from the educationalinformation database 402 of the appropriate third party content provider400 and integrating the educational content into a coupon (such as theEduSAVE™ document shown in FIG. 9). Further, according to one embodimentof the present invention, activation may further include delivering thecombined educational coupon to the patient via the selected deliverymode. Similarly, the combined educational coupon may be delivered to thepatient by transmitting the educational content to the HCP system 100 sothe educational coupon may be printed by the provider 101 for thepatient using the printer 130, or the educational coupon may bedelivered directly to the patient via one of the delivery modesdiscussed above.

In one embodiment, in which the supplemental program is a patientadherence service, the SP module activates the supplemental program byenrolling the patient in the patient adherence service. According toanother embodiment of the present invention, in which the activatedsupplemental program is a prescription reminder service, the SP moduleactivates the supplemental program by enrolling the patient in theprescription reminder service. In yet another embodiment of the presentinvention, in which the activated supplemental programs is anappointment reminder service, the SP module activates the supplementalprogram by enrolling the patient in the reminder service.

In the exemplified embodiments, the SP module enrolls the patient in theservice by transmitting the relevant data to the appropriate third partycontent provider 400, and the appropriate third party content provider400 signs the patient up for the service. For example, the relevant datamay include data relating to the patient, data relating to the patient'spast adherence, data relating to the electronic prescription, and datarelating to the patient's appointment schedule. However, in alternateembodiments of the present invention the SP module may enroll thepatient into the service without the use of the appropriate third partycontent provider 400. In such embodiments, the SP module may furthercomprise an enrollment engine in order to effectuate the enrollment ofthe patient in the appropriate service directly.

For example, in embodiments where the SP module further comprises anenrollment engine, the central portion 301 of the SP module wouldeffectuate the enrollment of patients into the services that wereactivated for them, without the need of the SP module transmittingpatient enrollment data to a third party content provider 400.

Referring back to FIG. 8c , after the SP module is done activating theeligible supplemental programs that have been confirmed by the healthcare provider 101, the SP module tailors the content relating to each ofthe activated supplemental programs for the specific delivery mode thatwas selected and confirmed by the provider 101, thereby completing step819. Generally, the central portion 301 of the SP module alters thespecific document depending on the specific delivery mode selected andconfirmed by the provider 101. For instance, if the delivery mode isselected to be via email, then the content is configured to be mosteasily viewable by a web browser. If the delivery mode is selected to bevia text/SMS to the patient's mobile phone, then the content isconfigured to be most easily viewable on the smaller screen of a mobiledevice. Further, if the delivery mode is selected so that the content isprinted at the printer 130, then the content is configured to be mosteasily printed.

It should be noted that if the supplemental program is a service, thestep of tailoring the content is typically not be performed. However, insome embodiments, the SP module may tailor a confirmation message of thepatient's enrollment in the service for delivery to the patient via thespecific delivery mode selected and confirmed above.

After the SP module tailors the content for the selected and confirmeddelivery mode, the SP module delivers the content of each of theactivated supplemental programs to the patient via the selected andconfirmed delivery modes, thereby completing step 820. Generally, thecentral portion 301 of the SP module will deliver the content if theselected delivery mode is to the patient's mobile phone, email, ormailing address. However, if the selected delivery mode is for thecontent to be printed at the printer 130, then the central portion 301of the SP module will transmit the content to the SP widget 302 residingon the HCP system 100, and the SP widget 302 thereby effectuates theprinting of the content by a printer 130 of the HCP system 100.

As noted above, according to one embodiment of the present invention,one or both of steps 819 and 820 may be considered part of theactivation step performed by the SP module. However, as also notedabove, the invention is not so limited and the processing performed bysteps 819 and 820 may also be considered separate, subsequent steps thatare performed after the activation step of the SP module.

In one alternate embodiment, the supplemental program data relating toall of the available supplemental programs resides on the SP system 300in its one or more databases. In such embodiments, the third partyvendor system 400 is omitted, and the central portion 301 of the SPmodule does not have to reach out to the third party vendor system 400to provide the patient with the documents or enroll the patient in theservices.

In another embodiment of the present invention, the third party vendorsystem 400 may transmit the document directly to the patient or enrollthe patient in the service upon receiving the request and the patientdelivery module data. Therefore, in such embodiments, the centralportion 301 of the SP module does not receive a document or confirmationsignal from the third party content provider 400.

Moreover, it should be noted that some of the services require thepatient to confirm their enrollment in the service. Therefore,enrollment cannot be fully effectuated by the SP module or the thirdparty vendor system 400. In such instance, the SP module or the thirdparty vendor system 400 would transmit the appropriate confirmation tothe patient via the delivery mode chosen by the provider. Thereafter, ifthe confirmation is received by the SP module, then the SP module wouldtransmit another enrollment signal back to the third party contentprovider 400. However, if the confirmation is received by the thirdparty content provider 400, then the third party content provider 400would enroll the patient in the service upon receiving the confirmationfrom the patient.

Further, in one embodiment of the present invention, a clinical staffpersonnel may perform the steps initiated by the provider 101. Aclinical staff personnel may be a nurse, an office or hospitaladministrator, or any other personnel involved in the health careindustry. In such embodiments, the clinical staff personnel would choosea previously prescribed substance to begin the process. Thereafter, theprocess would continue as described above, ultimately resulting in thepatient receiving a document (e.g., coupon, educational material, etc.)or being enrolled in a service.

Finally, it should be noted that the SP system 300, and specifically theSP module, of the present invention further comprises control andmanagement options for the provider 101 or an administrator of the HCPsystem 100. Therefore, using the control and management options, theprovider 101 or administrator may adjust the look, functionality, andprocesses of the SP module, including but not limited to, adding,removing, or editing provider and patient preferences, altering the GUIsgenerated and displayed by the SP module, etc.

Referring now to FIG. 16, a flow diagram of one method of acquiringpatient medication history data according to an embodiment of thepresent invention is illustrated. As shown, the process begins when theSP module residing on the SP system 300 retrieves data relating to anelectronic prescription from the EP module, thereby completing step1601. This may be accomplished in a manner similar to as discussedabove.

Upon receiving the electronic prescription data, the SP module parsesthe data to determine information relating to the patient, such as, butnot limited to the name of the patient, the age of the patient, andother identifying information. Further, the SP module may also parse theelectronic prescription data to determine information relating to theprescribed substance, the provider, and/or the payor. Next, the SPmodule transmits the retrieved patient data (potentially along withother relevant data) to a Medication History Poller System, therebycompleting step 1602.

The Medication History Poller System receives and stores the patientdata. Next, the Medication History Poller System transmits some of thepatient data along with a request for patient medication historyinformation to the pharmacy system 500 and/or the payor system 600,thereby completing step 1603. Thereafter, the Medication History PollerSystem receives medication history data relating to the patient from thepharmacy system 500 and/or the payor system 600. It should be noted thatin other embodiments of the present invention, the Medication HistoryPoller System may be part of the SP module. Further, it should be notedthat, as discussed above, the pharmacy system 500 may comprise aprescription routing sub-system 501 (e.g., Surescripts®) and theprescription filling sub-systems 502.

Upon receiving the medication history data relating to the patient, theMedication History Poller System transmits the medication history datarelating to the patient back to the SP module residing on the SP system300. It should be noted that in some embodiments of the presentinvention, the Medication History Poller System parses and analyzes themedication history data relating to the patient to determine adherencedata relating to the patient, including but not limited to, thepatient's adherence history in general, the patient's adherence historyover a specific time frame, and/or the patient's adherence history inrelation to a specific prescribed substance or plurality of prescribedsubstances for the same disease state.

Upon receiving the medication history data relating to the patient fromthe Medication History Poller System, the central portion 301 of the SPmodule uses the patient's medication history data when determiningeligibility of each of the plurality of available supplemental programs.Further, the central portion 301 of the SP module may further store thepatient's medication history information in either or both of therecords database 304 or a patient adherence database residing within thememory 313 of the SP system 300.

Referring now to FIGS. 17-28, event diagrams for supplementing patientand provider interactions to increase patient adherence according toother embodiments of the present invention are illustrated. It should benoted that the diagrams and methods described in reference to FIGS.17-28 are in no way limiting of the present invention.

Referring to FIG. 17, an event diagram of one method for acquiringprovider 101 preference data according to an embodiment of the presentinvention is illustrated. The method of FIG. 17 begins when the healthcare provider 101 logs into the EP module using their terminal 120.Thereafter, the EP module displays the startup screen to the provider101 on the display device 121. Next, the EP module prompts the SP widget302 to acquire provider preference information from the SP module. Uponbeing prompted by the EP module, the SP widget 302 calls the centralportion 301 of the SP module. Specifically, as exemplified in FIG. 17,the SP widget 302 calls a layout portion of the central portion 301 ofthe SP module to set the provider's preferences.

According to one embodiment of the present invention, the centralportion 301 of the SP module comprises two sub-portions, a layout and anadapter. The layout of the SP module generates the GUIs that aredisplayed to the provider 101 via the display device 121. The adapter ofthe SP module performs the transmission and receipt of data between thecentral portion 301 of the SP module and the other modules and systemsof the system 1000.

After being called by the SP widget 302, the layout calls the adapter toset the provider's preferences. Thereafter, the adapter obtains aplurality of different provider preferences offered by the SP module.Next, the layout determines whether any provider preferences had beenpreviously set by the provider 101 by searching the records database 304of the SP system 300. If all of the preferences have been set by theprovider 101, then the process ends. However, if there is at least oneunset provider preference, then the layout generates a GUI comprisingthe unset preferences and transmits the GUI to the SP widget 302. Uponreceiving the GUI, the SP widget 302 displays the GUI comprising theunset provider preferences to the provider 101 via the display device121.

Next, the provider 101 sets their preferences using the input means 122and via the GUI displayed on the display device 121. Thereafter, the SPwidget 302 transmits a signal to the layout to set the provider'spreferences. Upon receiving the provider's preferences, the layout callsthe adapter to set the provider's preferences, and the adapter storesthe provider preference information in the records database 304 of theSP system 300.

Referring to FIG. 18, an event diagram of one method for storingprovider 101 preference data according to an embodiment of the presentinvention is illustrated. The method begins after the provider 101selects their preferences in an appropriate GUI generated by the SPmodule and displayed via the display device 121. After selecting theirpreferences, the provider 101 actuates a save button on a GUI displayedby the SP widget 302. Actuating the save button causes the SP widget 302to call the layout of the SP module, which in turn calls the adapter ofthe SP module, which causes the SP module to store the prescribedpreference data in the records database 304.

Referring to FIG. 19, an event diagram of one method for cancellingprovider 101 preferences according to an embodiment of the presentinvention is illustrated. The method begins when the provider 101actuates a cancel button on a GUI displayed by the SP widget 302. Thiscauses the SP widget to close or cancel out of the preference GUI.

Referring to FIG. 20, an event diagram of one method for selectingsupplemental programs according to an embodiment of the presentinvention is illustrated. The method begins when the provider 101 usesthe EP module to create a new electronic prescription for a substance.After creating the electronic prescription, the provider 101 has theability to modify the prescription using the EP module. Thereafter, theEP module prompts the SP widget 302 with data relating to the electronicprescription. After being prompted by the EP module, the SP widget 302retrieves electronic prescription data relating to the electronicprescription from the EP module. Upon retrieving the electronicprescription data, the SP widget 302 transmits the data to the layout ofthe SP module, which in turn transmits the electronic prescription datato the adapter of the SP module.

Upon receiving the electronic prescription data, the adapter determinesif there are any programs, out of the plurality of availablesupplemental programs, for which the patient and the electronicprescription are eligible. If there are not any eligible programs, thenthe process ends. However, if there are eligible supplemental programs,then the layout of the SP module formats the supplemental program optionin a created GUI. Formatting may include a selection of the availabledelivery modes of each supplemental program and the generation of theGUIs that are to present the eligible supplemental programs to theprovider 101. At least one GUI is then displayed by the SP widget 302 tothe provider 101, so that the provider 101 may select and confirm whichof the eligible supplemental programs they would like activated for thepatient.

After the provider 101 makes a selection of eligible supplementalprograms, the SP widget 302 transmits the provider's selections tolayout of the SP module. The layout then transmits the provider'sselection to the adapter. Thereafter, the adapter retrieves the selectedsupplemental programs from the supplemental program database 303 andtransmits the selected eligible supplemental programs to the SP widget302 for display to the provider 101 via the display device 121.Thereafter, the provider 101 may print the eligible supplementalprograms for delivery to the patient.

Referring to FIG. 21, an event diagram of another method for selectingsupplemental programs according to an embodiment of the presentinvention is illustrated. The method of FIG. 21 is vastly similar to themethod of FIG. 20. It should be noted that processes performed by thelayout of the SP module in FIG. 20 are instead performed by the SPwidget 302 in the method of FIG. 21. Such a system and method may bepreferred to reduce the processing that occurs outside of the HCP system100.

Referring to FIG. 22, an event diagram of one method for presentingunexercised options according to an embodiment of the present inventionis illustrated. An unexercised option is an eligible supplementalprogram that the provider 101 did not select and confirm for activation.In one embodiment, the provider 101 may go back at a later time andselect unexercised options for activation by the SP module. This allowsthe provider 101 to activate supplemental programs for a patient outsideof the prescription writing workflow.

According to one embodiment of the present invention, the method beginswhen the provider 101 selects and views a prescription report generatedand display by the EP module. The EP module displays a prescriptionreport that comprises icon placeholders, the icon placeholdersrepresenting prescriptions that the provider 101 previously selected fora subsequent selection of eligible supplemental programs. Next, the EPmodule prompts the SP widget 302 with report prescription identificationdata. Although exemplified as being displayed by the EP module, itshould be noted that in alternate embodiments, the prescription reportmay be generated and displayed by the SP module.

Upon receiving the report prescription identification data, the SPwidget 302 calls the layout of the SP module for the unexercised optionsthat relate to each of the prescriptions identified by the reportprescription identification data. Thereafter, the adapter obtains theunexercised options off the identified prescriptions, and the layoutgenerates HyperText Markup Language (HTML) for placeholders for theunexercised options. Finally, the SP widget 302 instantiates iconUniform Resource Locators (URLs) for the prescription report.

Referring to FIG. 23, an event diagram of one method for displayingsupplemental program options according to an embodiment of the presentinvention is illustrated. This process begins when the provider 101actuates a program icon from the prescription report, discussed abovewith reference to FIG. 22. The EP module receives the provider's inputand prompts the SP widget 302 with the prescription identification. TheSP widget 302 then obtains the prescription content from theprescription identification, retrieves the supplemental program optionsfor the prescription and displays the supplemental program options tothe provider 101 in an overlay, similar to that exemplified in FIG. 15.It should be noted that the SP widget 302 does not have to reach backout to the central portion of the SP module, because in suchembodiments, the SP widget 302 comprises local memory in which theprogram options are stored.

Referring to FIG. 24, an event diagram of one method of the adapteracquiring unexercised options according to an embodiment of the presentinvention is illustrated. The method exemplified in FIG. 24 is used whenthe SP widget 302 does not have stored the unexercised options of theprescriptions identified in the prescription report cached locally onthe HCP system 100. As shown, the method of FIG. 24 begins with theadapter retrieving the unexercised options. Next, the adapter of the SPmodule checks to see if the prescription statuses are cached, anddetermines whether all the prescriptions have statuses that are cached.If not, then the adapter calls the SP module to get prescriptionstatuses for all uncached prescriptions, and the SP module retrieves theprescription statuses from the records database 304. Thereafter, theadapter combines the statuses of the prescriptions and returns URLs forthe unexercised options of each of the electronic prescriptions to theSP widget 302 for provider input.

Referring to FIG. 25, an event diagram of one method for displayingsupplemental program options according to an embodiment of the presentinvention is illustrated. The method begins with the SP widget 302displaying supplemental program options to the provider 101 via thedisplay device 121. The SP widget 302 then reads the electronicprescription context XML, and calls the adapter of the central portion301 of the SP module to get the options for the supplemental program.The SP module then evaluates the prescription context using the rulesengine to obtain a list of eligible supplemental programs for theelectronic prescriptions. After a list is obtained, the SP moduleobtains preference data relating to the provider 101 and the patient andcomposes a display for the supplemental program options. Finally, the SPwidget receives a GUI comprising the supplemental program options anddisplays the GUI to the provider 101 via the display device 121.

Referring to FIG. 26, an event diagram of one method for acquiringpatient preference data according to an embodiment of the presentinvention is illustrated. The method begins with the adapter of the SPmodule receiving a request for patient preference data from the SPwidget 302. The adapter determines whether the patient preferences arecached, and if so the adapter retrieves the patient preferences from thecached memory. If not, then the adapter retrieves the patientpreferences from the record database 304.

Referring to FIG. 27, an event diagram of another method for acquiringprovider 101 preference data according to an embodiment of the presentinvention is illustrated. The method of FIG. 27 is very similar to thatof FIG. 26. The method begins with the adapter of the SP modulereceiving a request for provider preference data from the SP widget 302.The adapter determines whether the provider preferences are cached, andif so the adapter retrieves the provider preferences from the cachedmemory. If not, then the adapter retrieves the provider preferences fromthe record database 304.

Referring to FIG. 28, an event diagram of one method for acquiringsupplemental programs from a third party content provider 400 accordingto an embodiment of the present invention is illustrated. The methodbegins with the adapter calling the SP module for supplemental programdocuments that have been selected and confirmed by the provider 101. TheSP module obtains one supplemental program at a time. The SP modulefirst determines which supplemental program to fetch and then retrievesthe third party content provider 400 identifiers for that particularsupplemental program. The identifiers comprise information relating tothe third party content provider 400 that stores the supplementalprogram. After retrieving the identifiers, the SP module calls the thirdparty content provider system 400.

Upon receiving the signal from the SP module, the third party contentprovider 400 determines whether the request is for a document or aservice based on the identifier of the supplemental program. If therequest is for a document, then the third party content provider 400generates the document. If the request is for a service, then the thirdparty content provider 400 configures the service for the patient.Thereafter, the third party content provider 400 transmits a response tothe SP module. The SP module then adds the document to a response andrepeats the process for each of the supplemental programs that wereselected and confirmed by the provider 101. After documents for all ofthe supplemental programs has been received by the SP module, the SPmodule returns the documents to the adapter, which in turn returns thedocuments to the SP widget 302 for presentation to the provider 101 viadisplay device 121 and provider input.

Referring to FIG. 29, a schematic diagram of a system for increasingpatient adherence through the activation of supplemental programsaccording to another embodiment of the present invention is illustrated.As shown, the system comprises an HCP system 100, an EP system 200, anSP system 300, and third party content providers 400.

EduSave™

Referring to FIG. 9, an EduSAVE™ 900 document according to oneembodiment of the present invention is illustrated. The EduSAVE™ 900document is one type of combined educational coupon document andcomprises a general information section 901, an educational informationsection 902, and a coupon section 903. The general information section901 may comprise information relating to the health care provider 101who issued the prescription for the patient, information relating to thepatient, information relating to the pharmacy filling sub-system 502,and/or information relating to the patient's payor (e.g., healthinsurance company). The educational information section 902 compriseseither general and/or specific information relating to the substancebeing prescribed and/or the disease state of the patient for which thesubstance is being prescribed. Finally, the coupon section 903 comprisescoupon information relating to a discount, a rebate, or a voucher forthe patient for the substance being prescribed. Although described ascombining general information, educational information, and couponinformation, it should be noted that in alternate embodiments of thepresent invention, the EduSAVE™ 900 document may comprises justeducational information and coupon information, or any combination ofhealth care provider 101 information, patient information, payorinformation, and pharmacy information along with educational informationand coupon information.

One reason the EduSAVE™ 900 document is beneficial is because itprovides for a single document that comprises both educationalinformation and coupon information. Therefore, when the patient bringsthe EduSAVE™ 900 document to their pharmacy for redemption of thecoupon, they are encouraged to read the educational information providedtherewith. Further, if the patient has any questions or concernsregarding the substance after they have left the provider's office, thepatient may easily access the provider's contact information on theEduSAVE™ 900 document.

According to one embodiment of the present invention, after anelectronic prescription for the substance is created by a health careprovider 101, the SP widget 302 retrieves data relating to theelectronic prescription from the thin-client portion of the EP module203. The SP widget 302 then transmits the electronic prescription datato the central portion 301 of the SP module residing on the SP system300, such that the central portion 301 of the SP module receives theelectronic prescription data. The electronic prescription data comprisesfirst patient data that is specific to the patient, first prescribedsubstance data that is specific to the prescribed substance, firstprovider data that is specific to the provider 101, and first payor datathat is specific to the payor. It should be noted that the specifics ofthe electronic prescription data are discussed in detail above.

However, the invention is not so limited, and in an alternate embodimentof the present invention, the electronic prescription data may notrelate to an electronic prescription currently being prescribed by ahealth care provider 101 for a patient, but rather relate to a refill, arenewal, or a previously prescribed substance. In such embodiments, theelectronic prescription data may be received by the SP module from oneof the other databases of the system 1000 (e.g., the EP database 201,the records database 304, the patient prescription history database 505,etc.). Stated another way, the electronic prescription data may, butdoes not necessarily have to be generated by a health care provider 101.

Once the central portion 301 of the SP module receives the electronicprescription data, the central portion 301 of the SP module retrievesadditional data prior to determining educational data and coupon datafor the prescribed substance. The additional (or second) data maycomprise one or more of patient data, prescribed substance data,provider data, and payor data. Further, the additional (or second)patient data may comprise patient adherence data. According to oneembodiment of the present invention, the additional (or second) data isretrieved by the SP module from the records database 304 of the SPsystem 300. However, it should be noted that the invention is not solimited and in alternate embodiments, the central portion 301 of the SPmodule may only retrieve a portion of the data listed herein or may notretrieve any additional data prior to determining educational data andcoupon data for the prescribed substance.

After receiving electronic prescription data, and possibly afterretrieving additional data from the records database 304, the SP moduledetermines educational data relating to the prescribed substance andcoupon data relating to the prescribed substance. In one embodiment ofthe present invention, the determination is accomplished by the centralportion 301 of the SP module in response to receiving the electronicprescription data. Thus, it may be said that the SP module determinesthe educational data and coupon data automatically upon receivingelectronic prescription data according to one embodiment of the presentinvention. In one embodiment of the present invention, the determinationof both the educational data and coupon data comprises the centralportion 301 of the SP module searching one or more databases, such asthe supplemental program database 303 or one of the databases 401, 402,403, 404 of the appropriate third party content provider 400, foreducational data and coupon data both relating to the prescribedsubstance. It should be noted that the determination of both theeducational data and coupon data may be accomplished by the centralportion 301 of the SP module using any combination of the first patientdata, first prescribed substance data, first provider data, and firstpayor received from the electronic prescription data, potentially alongwith any of the additional (or second) data (patient data, prescribedsubstance data, provider data, and payor data) retrieved by the SPmodule.

In one embodiment of the present invention, the determination ofeducational data and coupon data for the prescribed substance requiresthe central portion 301 of the SP module to determine both educationaldata and coupon data for which the patient is eligible based on theelectronic prescription. This is similar to as discussed above withreference to the determination of eligible supplemental programs.Therefore, in such embodiments, the educational data and coupon data maycomprise rules that must be met in order for the educational data andcoupon data to be eligible for the electronic prescription of thepatient. Thus, in accordance with one embodiment of the presentinvention, the determination of both the educational data and coupondata may be accomplished by the SP module in a manner similar to asdiscussed above with reference to supplemental programs (FIG. 8a andsteps 806-808).

However, the invention is not so limited, and in another embodiment ofthe present invention, the SP module simply transmits any combination ofdata (electronic prescription data and additional, retrieved data) to athird party system. This, in turn, causes the third party system todetermine the educational data and/or the coupon data upon receiving theappropriate data from the SP module. Thus, in this embodiment of thepresent invention, the third party system determines the educationaldata and/or the coupon data that relates to the prescribed substance.Finally, upon determining the educational data and/or the coupon data,the third party system transmits the educational data and/or the coupondata to the SP module. Therefore, it may be said that the centralportion 301 of the SP module receives the educational data and/or thecoupon data from one or more of the databases 401, 402, 403, 404 of theappropriate third party content provider 400.

Upon determining the educational data and coupon data that relates tothe prescribed substance, the central portion 301 of the SP moduleretrieves from one or more databases, such as the supplemental programdatabase 303 or one of the databases 401, 402, 403, 404 of theappropriate third party content provider 400, the educational data andthe coupon data. Thereafter, the central portion 301 of the SP modulecombines the educational data and the coupon data into a single datafile, which may be considered a combined educational coupon since thefile comprises both educational data and coupon data. It should be notedthat when the central portion 301 of the SP module combines theeducational data and the coupon data into a single data file, thecentral portion 301 of the SP module may combine a portion of or theentirety of the educational data and/or coupon data. Thus, the singledata file may comprise just a portion of either or both of theeducational data and the coupon data. Further, in one embodiment of thepresent invention, the single data file may be a text-based file, animage-based file, or a combined text and image based file. One exampleof a combined educational coupon is the EduSAVE™ 900 documentexemplified in FIG. 9.

Further, in one embodiment of the present invention, prior to generatinga single data file comprising the educational data and the coupon data,the central portion 301 of the SP module presents to a health careprovider 101, in the display device 121, a list of the education dataand the coupon data for selection and acceptance by the health careprovider 101. Thereafter, the central portion 301 of the SP modulegenerates the single data file, or the combined educational coupon, uponboth the educational data and the coupon data being selected andaccepted by the health care provider 101. It should be noted that thismay be accomplished in any manner discussed above with reference tosteps 811-814 of FIG. 8b . Finally, in one embodiment of the presentinvention, the central portion 301 of the SP module determines more thanone separate portion of educational data and/or coupon data and presentsthe one or more educational data and/or coupon data to the health careprovider 101 in a list via the display device 121. Thereafter, thehealth care provider 101 may select one or more of the educational dataand/or coupon data, and the central portion 301 of the health careprovider 101 combines the one or more of the educational data and/orcoupon data into a single data file, the single data file being acombined educational coupon. Thus, the combined educational coupon isnot limited to just one educational data file and one coupon data file,but may comprise more than one educational data file and/or coupon datafile. Finally, after generating the combined educational coupon, thecentral portion 301 of the SP module may then store the combinededucation coupon in one or more databases (e.g., the records database304 or the supplemental program database 303) of the SP system 300 forsubsequent applications.

Finally, after the central portion 301 of the SP module has generatedthe single data file comprising the educational data and coupon datarelating to the prescribed substance, the central portion 301 of the SPmodule may transmit the single data file to one or more systems ordevices. These include, but are not limited to, a pharmacy fillingsub-system 502, an HCP system 100, and a patient computer device. It maybe beneficial to transmit the single data file to a pharmacy fillingsub-system 502 so that the patient does not have to remember to bringthe combined educational coupon with them when picking up theprescription. Rather, the combined educational coupon is waiting forthem at the pharmacy filling sub-system 502, such that the pharmacistmay automatically deduct the coupon from the purchase price of theprescription and the educational material may be provided to the patientupon receiving their prescription. Further, it may be beneficial totransmit the single data file to the HCP system 100 so that the HCPsystem 100 may make the combined educational coupon available to patientwhile they are still in the presence of their health care provider 101.Therefore, if the patient has any questions or concerns, they mayimmediately speak with their health care provider 101 upon receiving thecombined educational coupon. Finally, it may be beneficial to transmitthe single data file to a patient computer device, such as a personalcomputer, smart phone, printer, fax machine, or other electronic deviceowned or controlled by the patient. This allows the patient to receiveand view the combined educational coupon at their convenience.

Nonetheless, it should be noted that in accordance with one embodimentof the present invention, the central portion 301 of the SP modulegenerates a combined educational coupon using the process describedabove with respect to supplemental programs. In such embodiments, thecentral portion 301 of the SP module parses out educational informationdata from an eligible supplemental program that relates to educationalmaterial, and coupon data from an eligible supplemental program thatrelates to a coupon. Thereafter, the central portion 301 of the SPmodule combines the educational information data and the coupon data,potentially along with other general data (e.g., provider data, patientdata, etc.) into a single data file to create the combined educationalcoupon. Thereafter, the central portion 301 of the SP module may storethe combined education coupon in the supplemental program database 303of the SP system 300 for subsequent applications. Further, aftercreating the combined educational coupon, the central portion 301 of theSP module may transmit the combined educational coupon to the HCP system100 as a single data file.

Further, it should be noted that in one embodiment of the presentinvention, the central portion 301 of the SP module may be considered anon-transitory computer-readable storage medium that is encoded withinstructions which, when executed by the processor 311, perform a methodof receiving data relating to an electronic prescription of a prescribedsubstance for a patient; searching one or more databases for educationaldata relating to the prescribed substance and coupon data relating tothe prescribed substance; determining educational data relating to theprescribed substance and coupon data relating to the prescribedsubstance; retrieving from the one or more databases the educationaldata relating to the prescribed substance and the coupon data relatingto the prescribed substance; and generating a single data filecomprising the educational data relating to the prescribed substance andthe coupon data relating to the prescribed substance.

Finally, it should be noted that in one embodiment of the presentinvention, the SP system 300 may be considered a computer system forelectronically generating educational coupons for a prescribedsubstance, which comprises a processor 311; a storage device 313; anetwork interface 312; and instructions residing on the storage unit313, which when executed by the processor 311, causes the processor 311to: a) receive electronic prescription data for a prescribed substancefor a patient; b) determine educational data relating to the prescribedsubstance and coupon data relating to the prescribed substance; and c)generate a single data file comprising the educational data relating tothe prescribed substance and the coupon data relating to the prescribedsubstance.

Tailoring General and Specific Educational Content

As noted above, the supplemental programs comprise both generaleducational content and specific educational content. In one embodimentof the present invention, the general educational content comprisesinformation relating to the prescribed substance, while the specificeducational content comprises information relating, not only to theprescribed substance, but also the specific diagnostic reason(s) thatthe substance was prescribed to the patient, such as but not limited to,the specific disease(s) for which the substance was prescribed, alongwith a wide variety of signs, symptoms, abnormal findings, complaints,social circumstances, and external causes of injury or disease for whichthe substance was prescribed. Thus, the educational content (ormaterial), both general and specific, is tailored to the specific needsand diagnoses of the patient.

Similar to as discussed above and according to one embodiment of thepresent invention, after an electronic prescription for the substance iscreated by a health care provider 101, the SP widget 302 retrieves datarelating to the electronic prescription from the thin-client portion ofthe EP module 203. Further, the SP widget 302 may also retrieve adiagnostic code that is entered by the health care provider 101.Specifically, the provider 101 enters a diagnostic code into the SPwidget 302 using the input device 122 of the terminal 120. Thediagnostic code may be entered prior to, during, or after the creationof the electronic prescription by the health care provider 101.

A diagnostic code is a string of characters and/or numbers that are usedto represent medical diseases and/or a wide variety of signs, symptoms,abnormal findings, complaints, social circumstances, and external causesof injury or disease. According to one embodiment, the diagnostic codeis entered or provided by the health care provider 101 and provides amore specific reasoning as to why the patient is being prescribed aparticular substance. For example, in one embodiment, the diagnosticcode is an International Classification of Diseases, Ninth Revision(ICD-9) code entered by the provider 101 during the patient's visit.

After receiving data relating to an electronic prescription and adiagnostic code, the SP widget 302 then transmits the electronicprescription data and the diagnostic code to the central portion 301 ofthe SP module residing on the SP system 300, such that the centralportion 301 of the SP module receives the electronic prescription dataand the diagnostic code. It should be noted that the diagnostic codemay, but does not necessarily have to, be received in conjunction withthe electronic prescription data. As discussed in detail above, theelectronic prescription data comprises first patient data that isspecific to the patient, first prescribed substance data that isspecific to the prescribed substance, first provider data that isspecific to the provider 101, and first payor data that is specific tothe payor. Further, in one embodiment of the present invention, theelectronic prescription data further comprises a National Drug Codeidentifier of the prescribed substance. The National Drug Codeidentifier is a unique product identifier for prescribed substances thatare intended for human use. Finally, it should be noted that in oneembodiment of the present invention, the electronic prescription datacomprises the diagnostic code.

Further, in an alternate embodiment of the present invention, theelectronic prescription data does not relate to an electronicprescription currently being prescribed by a health care provider 101for a patient, but rather relates to a refill, a renewal, or apreviously prescribed substance. In such embodiments, the electronicprescription data may be received by the SP module from one of the otherdatabases of the system 1000 (e.g., the EP database 201, the recordsdatabase 304, the patient prescription history database 505, etc.).Stated another way, the electronic prescription data may, but does notnecessarily have to be generated by a health care provider 101.

Once the central portion 301 of the SP module receives the electronicprescription data and the diagnostic code, the central portion 301 ofthe SP module retrieves additional data prior to determining general andspecific educational data. As discussed in more detail above, theadditional (or second) data may comprise one or more of patient data,prescribed substance data, provider data, and payor data. Further, theadditional (or second) patient data may comprise patient adherence data.According to one embodiment of the present invention, the additional (orsecond) data is retrieved by the SP module from the records database 304of the SP system 300. However, it should be noted that the invention isnot so limited and in alternate embodiments, the central portion 301 ofthe SP module may only retrieve a portion of the data listed herein ormay not retrieve any additional data prior to determining general andspecific educational data.

After receiving electronic prescription data and the diagnostic code,and possibly after retrieving additional data from the records database304, the central portion 301 of the SP module searches one or moredatabases, such as the supplemental program database 303 or one of thedatabases 401, 402, 403, 404 of the appropriate third party contentprovider 400, for general educational data and specific educational databoth relating to the prescribed substance. The general educational datarelates to the prescribed substance, but is independent of thediagnostic code. Thus, the general educational data comprises broad andwide-ranging information that relates generally to the prescribedsubstance or the disease state for which the substance was prescribed tothe patient. For example, general educational data may compriseinformation relating to high blood pressure in general.

By contrast, the specific educational data relates to the prescribedsubstance and is based on the received diagnostic code. Thus, thespecific educational data comprises specific information about theparticular prescribed substance or the disease state of the prescribedsubstance, and is particular to the exact reasons for which the provider101 has written the prescription for the patient. For example, specificeducational data may comprise information relating to malignanthypertension or renal hypertension, whereby the general educational datasimply relates to high blood pressure in a broader or more generalsense. Stated another way, the specific educational content may relateto one or more of the specific disease(s) for which the substance wasprescribed, and/or the signs, symptoms, abnormal findings, complaints,social circumstances, and/or external causes of injury or disease forwhich the substance was prescribed to the patient. Further, as discussedin detail above, the educational data (both general and specific) mayrelate to an educational document or an educational service, asdiscussed above in more detail.

It should be noted that the determination of both the general andspecific educational data may be accomplished by the central portion 301of the SP module using any combination of the diagnostic code, the firstpatient data, first prescribed substance data, first provider data, andfirst payor received from the electronic prescription data, potentiallyalong with any of the additional (or second) data (patient data,prescribed substance data, provider data, and payor data) retrieved bythe SP module. Further, in one embodiment of the present invention, thegeneral educational data is searched using the National Drug Codeidentifier, along with any combination of the electronic prescriptiondata and retrieved data discussed above. Similarly, it should be notedthat the specific educational data is searched using the diagnostic codereceived by the central portion 301 of the SP module, along with anycombination of the electronic prescription data and retrieved datadiscussed above.

In one embodiment of the present invention, in order for the centralportion 301 of the SP module to determine both the general educationaldata and the specific educational data, the central portion 301 of theSP module must also determine which general and specific educationaldata the patient is eligible for based on the electronic prescription.This is similar to as discussed above with reference to thedetermination of eligible supplemental programs. Therefore, in suchembodiments, the general educational data and the specific educationaldata may comprise rules that must be met in order for the generaleducational data and the specific educational data to be eligible forthe electronic prescription of the patient. Moreover, in accordance withone embodiment of the present invention, the determination of both thegeneral educational data and the specific educational data may beaccomplished by the central portion 301 of the SP module in a mannersimilar to as discussed above with reference to supplemental programs(FIG. 8a and steps 806-808).

However, the invention is not so limited, and in another embodiment ofthe present invention, the SP module simply transmits any combination ofdata (electronic prescription data, diagnostic code, National Drug Codeidentifier, and additional, retrieved data) to a third party system.This, in turn, causes the third party system to determine the generaleducational data and/or the specific educational data upon receiving theappropriate data from the SP module. Thus, in this embodiment of thepresent invention, the third party system determines the generaleducational data and/or the specific educational data that relates tothe prescribed substance. Finally, upon determining the generaleducational data and/or the specific educational data, the third partysystem transmits the general educational data and/or the specificeducational data to the SP module. Therefore, it may be said that thecentral portion 301 of the SP module receives the general educationaldata and/or the specific educational data from one or more of thedatabases 401, 402, 403, 404 of the appropriate third party contentprovider 400.

Upon determining the general educational data and the specificeducational data that relates to the prescribed substance and thediagnostic code, the central portion 301 of the SP module retrieves fromone or more databases, such as the supplemental program database 303 orone of the databases 401, 402, 403, 404 of the appropriate third partycontent provider 400, the general educational data and the specificeducational data. According to one embodiment of the present invention,the central portion 301 of the SP module retrieves two data files, afirst data file that is the general educational data and a second datafile that is the specific education data. Thereafter, the centralportion 301 of the SP module may combine the first data file (generaleducational data) and the second data file (specific educational data)into a single data file, thus creating a single data file that comprisesboth general educational data and specific educational data. It shouldbe noted that when the central portion 301 of the SP module combines thegeneral and specific educational data into a single data file, thecentral portion 301 of the SP module may combine a portion of or theentirety of the general educational data and the specific educationaldata. Thus, the single data file may comprise just a portion of eitheror both of the general and specific educational data. Moreover,according to one embodiment of the present invention, the centralportion 301 of the SP module may combine one or more general educationdata file with one or more specific educational data file. However, itshould be noted that the invention is not so limited, and in someembodiments of the present invention, the general educational data andthe specific educational data is not combined into a single data file.

Further, in one embodiment of the present invention, the central portion301 of the SP module presents to a health care provider 101, in thedisplay device 121, a list that comprises the general education data andthe specific educational data for selection and acceptance by the healthcare provider 101. In such embodiments, each of the general educationdata and the specific education data presented in the display device 121is selectable and de-selectable by the health care provider 101 usingthe input device 122. It should be noted that the display of the listand the selection and acceptance of the general and specific educationaldata may be accomplished in any manner similar to as discussed abovewith reference to supplemental programs in steps 811-814 of FIG. 8b .Further, it should be noted that the list is not limited to only onegeneral educational data file and one specific educational file, butrather may include any number of general and/or specific educationalfiles for selection and acceptance by the health care provider 101.

According to one embodiment of the present invention, after a list ofthe general education data and the specific educational data ispresented in the display device 121 to the health care provider 101 forprovisioning to the patient, the central portion 301 of the SP modulemakes the general educational data and the specific educational datathat is selected and confirmed by the health care provider 101 availableto the patient. In one embodiment, this is accomplished by the SP moduletransmitting the general education data and the specific educationaldata that is selected and confirmed by the health care provider 101 to apatient computer device. This may be accomplished using at least one ofemail, SMS. WAP, and a mobile application.

Therefore, the diagnostic code may be used, in addition to theelectronic prescription data and any additional retrieved data, by thecentral portion 301 of the SP module to determine if there is bothgeneral educational data and specific educational data for which thepatient is eligible. Therefore, by using a diagnostic code (e.g., theICD-9 code) to determine if there is any eligible specific educationaldata relating to why the prescribed substance was prescribed to thepatient, the present invention may provide both general and specificeducational material to the patient. For instance, the patient mayreceive general information relating to the substance they are beingprescribed or the disease state in which they are diagnosed, while alsoreceiving specific educational material directed to the specificreason(s) the patient has been prescribed the particular substance. Thisis beneficial because the educational documents and/or services help thepatient in understanding not only their general health concerns andprescribed substances, but also their specific health concerns alongwith their specific diagnoses. Thus, the educational material (bothgeneral and specific) that is made available to the patient may betailored to the specific needs and diagnoses of the patient.

Further, it should be noted that in one embodiment of the presentinvention, the central portion 301 of the SP module may be considered anon-transitory computer-readable storage medium that is encoded withinstructions which, when executed by the processor 311, perform a methodof receiving electronic prescription data for a prescribed substance fora patient, said electronic prescription data including a diagnosticcode; searching one or more databases to determine: (1) generaleducational data relating to the prescribed substance independent of thediagnostic code; and (2) specific educational data relating to theprescribed substance based on the diagnostic code; and presenting to ahealth care provider, in a display device, a list of the generaleducational data and the specific educational data determined in step b)for provisioning to the patient.

Finally, it should be noted that in one embodiment of the presentinvention, the SP system 300 may be considered a computer system forelectronically generating educational coupons for a prescribedsubstance, which comprises a processor 311; a storage device 313; anetwork interface 312; and instructions residing on the storage unit313, which when executed by the processor 311, causes the processor 311to: a) receive electronic prescription data for a prescribed substancefor a patient, said electronic prescription data including a diagnosticcode; b) search one or more databases to determine: (1) generaleducational data relating to the prescribed substance independent of thediagnostic code; and (2) specific educational data relating to theprescribed substance based on the diagnostic code; and c) present to ahealth care provider, in a display device, a list of the generaleducational data and the specific educational data determined in step b)for provisioning to the patient.

Method of Using Cohorts to Determine Effectiveness of SupplementalPrograms

According to another embodiment of the present invention, the system1000 described above may be used to determine the effectiveness ofsupplemental programs on patient adherence through the use of aplurality of cohorts. Generally, as used herein, a cohort is a group ofhealth care providers 101 who activate the same supplemental programsfor a particular prescribed substance. As discussed in more detailbelow, in accordance with one embodiment of the present invention aplurality of cohorts, each comprising different permutations (orgroupings) of supplemental programs, are used to determine therespective effectiveness of the different permutations of supplementalprograms on patient adherence to one or more prescribed substances.

According to one embodiment of the present invention, a method ofdetermining the effectiveness of a plurality of available supplementalprograms on patient adherence comprises four steps: (1) defining aplurality of cohorts, each cohort comprising at least one health careprovider; (2) receiving data relating to an electronic prescription ofthe one or more prescribed substances generated by a health careprovider and activating the supplemental programs associated with thecohort to which the health care provider belongs; (3) receiving patientadherence data relating to electronic prescriptions for the one or moreprescribed substances issued by the plurality of health care providers;and (4) analyzing the patient adherence data to determine theeffectiveness of the different permutations of the supplemental programson patient adherence.

Although the processes and functions described below are described andexemplified as being performed by the SP module in general, it should beunderstood that the invention is not so limited, and in alternateembodiments the processes and function described herein with referenceto cohorts may be performed by any single portion, the central portion301 or the SP widget 302, or a combination of the portions of the SPmodule.

Referring to FIG. 4, it should be noted that the memory 313 of theserver 310 of the SP system 300 further comprises a cohort database 305,a patient adherence generation module 306, and a patient adherencedatabase 307. As explained in more detail below, the cohort database 305stores, among other things, information relating to a plurality ofhealth care providers 101 who are part of at least one cohort, alongwith information relating to each of the cohorts defined by the SPmodule. For instance, after defining the cohorts, the SP module storesinformation relating to each cohort (e.g., the target drug data, theprovider cohort data, the assigned health care providers 101, theassigned permutation of supplemental programs, the cohort rules, themaximum counter, etc.) in the cohort database 305 of the SP system 300.

As also discussed in more detail below, the patient adherence generationmodule 306 receives data relating to the patient's prescription historyfor the target drug from the pharmacy system 500 and/or the payor system600. This information is referred to as patient medication history data.After receiving the patient medication history data, the patientadherence generation module 306 stores the patient medication historydata in one or more databases, such as, but not limited to the patientadherence database 307. Thereafter, the patient adherence generationmodule 306 analyzes the patient medication history data to generatepatient adherence data from the received patient medication historydata. Finally, the patient adherence generation module 306 stores thepatient adherence data in the patient adherence database 307 for furtherprocessing. In certain embodiments, the patient adherence generationmodule 306 obtains all of the drug fill data that it can for a patientfor all drugs, not just the drugs for which the patient hasprescriptions. Although in the exemplified embodiment the patientadherence generation module 306 does not use the data for drugs withouta known prescription, it is contemplated that in certain otherembodiments the patient adherence generation module 306 could use thedata from both drugs with a known prescription and drugs without a knownprescription.

Generally, and as discussed in more detail below, patient medicationhistory data comprises information relating to the medication history ofthe patient and the patient's fill history for various prescriptions. Asalso discussed in more detail below, patient adherence data comprisesinformation relating to the patient's adherence to previousprescriptions. Although sometimes described with reference to the targetdrug of a cohort, it should be noted that the patient medication historydata and patient adherence data is not so limited, and in alternateembodiments of the present invention the patient medication history dataand/or the patient adherence data may refer to prescriptions for anysubstances of the patient. Moreover, it should be noted that the patientadherence database 307 may store patient adherence data relating tovarious different cohorts for the same target drug, along with patientadherence data relating to various different cohorts for differenttarget drugs. One non-limiting example of a patient adherence generationmodule 306 is the HMACS™ system by DrFirst®.

As discussed in more detail below, the patient adherence generationmodule 306 receives the patient medication history data either directlyor indirectly from another system, such as but not limited to thepharmacy system 500 and the payor system 600. After receiving thepatient medication history data, the patient adherence generation module306 generates the patient adherence data using one or more algorithmsthat are stored in the patient adherence database 307. Thereafter, theSP module receives the patient adherence data from the patient adherencedatabase 307 so that the SP module may parse and analyze the patientadherence data by cohort to determine the effectiveness of a pluralityof different permutations of supplemental programs on patient adherence.

As noted above and as discussed in more detail below, the patientadherence database 307 stores information relating to one or morepreviously prescribed substances of one or more patients, such as, butnot limited to, patient medication history data and patient adherencedata. It should be noted that in other embodiments of the presentinvention, prescription data, patient medication history data, andpatient adherence data may be stored on separate databases.

Since, in the exemplified embodiment of FIG. 4, the patient adherencegeneration module 306 resides within the memory 313 of the SP system300, it may be said that the SP system 300 receives patient medicationhistory data, parses the patient medication history data, and analyzesthe data to generate adherence data for the patient for the target drug.Nonetheless, it should be noted that in other embodiments of the presentinvention, the patient adherence generation module 306 may reside onanother system or within its own system as part of system 1000.Similarly, in other embodiments of the present invention, the adherencedatabase 307 may also reside within the memory of another system ofsystem 1000. For example, according to one embodiment of the presentinvention and as discussed in more detail below, the patient adherencegeneration module 306 resides on a separate system as part of the system1000, and the adherence database 307 resides within the memory of theseparate system, such that the patient adherence generation module 306and adherence database 307 reside on their own separate system (e.g., apatient adherence system).

1. Defining a Plurality of Cohorts

As noted above, the first step of determining the effectiveness of aplurality of supplemental programs on patient adherence comprises thedefining (or creating) of a plurality of cohorts, whereby each cohortcomprises a plurality of health care providers 101. Generally, theprocess of defining the plurality of cohorts comprises two steps: (1)assigning a sub-set of a plurality of health care providers 101 to eachof the plurality of cohorts; and (2) assigning a different permutationof supplemental programs to each of the plurality of cohorts.

As used herein, the plurality of cohorts is used to test theeffectiveness of different permutations of supplemental programs onpatient adherence to a particular substance or a plurality of prescribedsubstances for a particular disease state. Therefore, each cohort out ofthe plurality of cohorts (of the same program cohort group) all relateto the same prescribed substance(s). For example, a particularprescribed substance, such as Lipitor®, may be assigned to a pluralityof cohorts (of the same program cohort group), so that differentpermutations of supplemental programs may be tested to determine theireffectiveness on the patients' adherence to Lipitor®. For furtherexample, a plurality of prescribed substances, such as Lipitor®,Lescol®, Mevacor®, Pravachol®, and Zocor®, for the same disease state,high cholesterol, may be assigned to a plurality of cohorts so thatdifferent permutations of supplemental programs may be tested todetermine their effectiveness on the patients' adherence to theprescribed substance for that particular disease state (highcholesterol).

It should be noted that when a plurality of cohorts are all related toone another (e.g., are used together as a single test group for the sameprescribed substance(s)) they are considered to be part of the sameprogram cohort group. Therefore, according to one embodiment of thepresent invention, a program cohort group is a group of a plurality ofcohorts for the same prescribed substance or plurality of prescribedsubstances for a particular disease state. However, it should be notedthat there may be different program cohort groups that relate to thesame prescribed substance. Further, as discussed in more detail below,the related program cohort group for each of the plurality of cohorts isstored within the cohort database 305 of the SP system 300.

As noted above, each cohort of a plurality of cohorts is assigned asub-set of health care providers 101. Further, as discussed in moredetail below, each sub-set of health care providers 101 has acommonality of prescribing factors with relation to the prescribedsubstance(s) of the program cohort group. It should be noted thatalthough a provider 101 may be associated with only one out of aplurality of cohorts for a particular prescribed substance (or pluralityof prescribed substances for a particular disease state), a provider 101may be a part of other, unrelated program cohort groups. Stated moresimply, a provider 101 may only be associated with one cohort of aparticular program cohort group, but the provider 101 may be associatedwith different cohorts of different program cohort groups.

Referring to FIG. 30, a flow chart of a method 3000 for defining aplurality of cohorts of a program cohort group according to oneembodiment of the present invention is illustrated. To begin, the SPmodule first receives target drug data, thereby completing step 3001.The target drug data comprises information relating to a particularprescribed substance or a plurality of prescribed substances for aparticular disease state to which the plurality of cohorts will relate.After receiving the target drug data, the SP module stores the targetdrug data in the cohort database 305 of the SP system 300 in correlationwith a program cohort group.

Therefore, the target drug data defines for which prescribedsubstance(s) the effectiveness of the available supplemental programs onpatient adherence will be analyzed by the SP module. Stated another way,the SP module defines a plurality of cohorts to analyze theeffectiveness of the available supplemental programs on patientadherence for only the prescribed substance(s) identified by the targetdrug data. For example, using the examples set forth above, the targetdrug data may be just Lipitor® or it may be the combination of Lipitor®,Lescol®, Mevacor®, Pravachol®, and Zocor®. For purposes of simplicity,the term “target drug” will be used to denote the particular prescribedsubstance or the plurality of prescribed substances for a particulardisease state that is defined by the received target drug data. Thus,the term target drug may comprise one or more than one prescribedsubstance.

According to one embodiment of the present invention, the target drugdata is received by the SP module via inputs from the administrator ofthe SP system 300. It should be noted that an administrator of the SPsystem 300 may be one or more individuals who have access to and maycontrol the SP system 300 (including the modules residing thereon). Insuch embodiments, by defining the target drug data, the administrator ofthe SP system 300 selects the particular prescribed substance(s) thatwill be used for the cohorts of a program cohort group. It should benoted that the invention is not so limited, and in alternate embodimentsthe SP module may receive the target drug data from a pharmaceuticalcompany or the target drug data may be derived jointly by both theadministrator of the SP system 300 and a third party (e.g., apharmaceutical company).

Still referring to FIG. 30, after the SP module receives the target drugdata, the SP module retrieves provider cohort data from the cohortdatabase 305 of the SP system 300, thereby completing step 3002. Asdiscussed in more detail below, the provider cohort data comprisesinformation relating to each of the plurality of health care providers101, and more specifically, comprises information relating to theprovider's history of prescribing the target drug.

According to one embodiment of the present invention, the providercohort data comprises a decile level for one or more prescribedsubstances and/or a medical specialty of the health care provider 101.As understood in the art, a decile level is a rating or level, on ascale from 1 to 10, for which the provider 101 has prescribed aparticular prescribed substance or prescribed substances for aparticular disease state. For example, a provider 101 who has prescribedLipitor® more than another provider 101 will have a higher decile level.Therefore, the SP module assigns a sub-set of the plurality of healthcare providers 101 to each of the plurality of cohorts such that theaverage decile level of the health care providers 101 assigned to eachcohort of a program cohort group is similar. By assigning health careproviders 101 to the cohorts based on their decile level, each of theplurality of cohorts of a program cohort group has a commonality ofprescribing factors relating to the target drug. However, as discussedbelow, the invention is not so limited and in alternate embodiments, theSP module assigns health care providers 101 to a cohort based on otherfactors so long as each cohort of a program cohort group has acommonality of prescribing factors.

As noted above, the use of a decile level is one way to define thecohorts such that there is a commonality of prescribing factors betweenthe health care providers 101 of each cohort of a program cohort group.The present invention may utilize any number of other methods to assignhealth care providers 101 such that each cohort has a commonality ofprescribing factors. Therefore, the commonality of prescribing factorsrelates to the target drug, ensures that each cohort has a similarcross-section of providers 101 as they relate to the target drug, andmay be defined by the SP module in any manner. For example, the SPmodule may define the commonality of prescribing factors between theplurality of health care provider 101 as a decile level, as a rate ofprescription of the prescribed substance(s) defined by the target drugdata, or a total number of prescriptions written by each provider 101for the prescribed substance(s) defined by the target drug data. Acommonality of prescribing factors could also be determined by the agegroups of the prescriber's patients, or age and demographics of the townin which the prescriber is located.

Still referring to FIG. 30, after retrieving the provider cohort datarelating to each of the plurality of health care providers 101, the SPmodule assigns a sub-set of a plurality of health care providers 101 toeach of a plurality of cohorts based on the retrieved provider cohortdata, thereby completing step 3003. Stated another way, the SP moduleassigns at least one health care provider 101, and preferably more thanone health care provider 101 to each of the plurality of cohorts of aprogram cohort group. In one embodiment of the present invention, the SPmodule assigns the health care providers 101 to the plurality of cohortsusing the provider's NPI numbers. After assigning a sub-set of theplurality of providers 101 to each of the cohorts of a program cohortgroup, the SP module stores the provider's NPI number in the cohortdatabase 305 in association with the cohort identifier, as discussedbelow in more detail. However, the invention is not so limited and inalternate embodiments the assignment of health care providers 101 tocohorts may be done using name or any other identifying factor of thehealth care providers 101.

Further, it should be noted that the plurality of health care providers101 that is broken down in sub-sets and assigned to the cohorts of aprogram control group may be chosen by the SP module via one or moremethods. For example, the plurality of health care providers 101 may beselected using geographic location, commonality of prescribing factors,and/or input by an administrator of the SP module.

Referring to FIG. 31, a schematic diagram depicting how the SP moduledefines a plurality of cohorts according to one embodiment of thepresent invention is illustrated. The SP module retrieving provider 101information (e.g., provider NPI numbers) from the cohort database 305 orthe records database 304. After retrieving the provider 101 information,the SP module defines a plurality of cohorts such that each of theplurality of cohorts comprises a sub-set of the plurality of health careproviders 101. It should be noted that in the preferred embodiment, eachof the plurality of health care providers 101 is assigned to only onecohort of a program cohort group. For example, as shown in FIG. 31,cohort 1 is defined to comprise health care providers (HCP) 101 number1, 3 and 8, cohort 2 is defined to comprise HCP 101 number 2, 4, and 10,cohort 3 is defined to comprise HCP 101 number 5, 9, and 11, and cohort4 is defined to comprise HCP 101 number 6, 7, and 12. Although notexemplified, the health care providers 101 are assigned to each of thecohorts such that each cohort has a commonality of prescribing factorsbetween their assigned providers 101.

Although four cohorts are defined by the SP module in the exampleexemplified by FIG. 31, the invention is not so limited and in alternateembodiments the SP module may define any number of cohorts for aparticular program cohort group. Stated another way, the plurality ofcohorts comprises at least two cohorts and may comprise any number ofcohorts. Further, although each cohort of FIG. 31 is assigned only threehealth care providers 101, the invention is not so limited and inalternate embodiments, each cohort may be defined to comprise any numberof health care providers 101 so long as each cohort has a commonality ofprescribing factors between its assigned health care providers 101.Therefore, according to one embodiment of the present invention,different cohorts of a program cohort group may comprise a differentnumber of health care providers 101.

Referring back to FIG. 30, and as mentioned above, alter assigning asub-set of health care providers 101 to each of the plurality ofcohorts, the SP module generates a cohort identifier for each of theplurality of cohorts. In one embodiment, the cohort identifier is aunique string of numbers used by the SP module to identify thatparticular cohort. After generating a cohort identifier for each of theplurality of cohorts, the SP module associates the cohort identifierwith each of the plurality of health care providers 101 of thatparticular cohort, thereby completing step 3004. Therefore, each healthcare provider 101 of a sub-set of health care providers 101 of aparticular cohort is associated with the same unique cohort identifierof that cohort. Thereafter, the SP module stores the association ofhealth care provider 101 (e.g. NPI number) and cohort identifier in thecohort database 305 of the SP system 300. As a result, and as discussedin more detail below, the SP module may more easily identify theassociated cohort of a particular health care provider 101 using theprovider's associated cohort identifier stored in the cohort database305.

As noted above and in accordance with one embodiment of the presentinvention, the assignment of providers 101 between cohorts isaccomplished by the SP module via inputs from the administrator of theSP system 300. In one embodiment, the instructions from theadministrator of the SP system 300 specify which provider 101 isassigned to which cohort. In another embodiment, the instructions fromthe administrator of the SP system 300 specify rules by which theproviders 101 will be assigned to each cohort (e.g., geographiclocation, specialty, prescribing history of the target drug, etc.). Inyet another embodiment of the present invention, the SP module does notreceive instructions, but rather automatically assigns providers 101 toeach cohort using an algorithm stored within the cohort database 305,such that each cohort has a commonality of prescribing factors.

After assigning a sub-set of a plurality of health care providers 101 toeach of the cohorts, the SP module assigns a different permutation ofeligible supplemental programs to each cohort. As discussed above, thesupplemental program database 303 of the SP system 300 stores generalsupplemental program data, including, but not limited to the name of thesupplemental program, general information relating to the supplementalprogram, and the rules of each supplemental program. As noted above,each supplemental program comprises rules (non-cohort rules), such as aparticular prescribed substance(s) for which the program is eligible andinformation relating to which patients are eligible for the supplementalprogram.

Still referring to FIG. 30, prior to assigning a different permutationof eligible supplemental programs to each cohort, the SP moduledetermines which supplemental programs out of the plurality of availablesupplemental programs are eligible for target drug of the plurality ofcohorts, thereby completing step 3005. According to one embodiment ofthe present invention, eligibility is determined by the SP module basedon the target drug defined by the received target drug data. Therefore,the SP module determines which supplemental programs out of theavailable supplemental programs are eligible for the cohorts based onthe received target drug data.

After determining which of the available supplemental programs areeligible for the plurality of cohorts based on the received target drugdata, the SP module retrieves information relating to the plurality ofeligible supplemental programs from the supplemental program database303 of the SP system 300. After retrieving information relating to theplurality of eligible supplemental programs, the SP module defines aplurality of different permutations of the eligible supplementalprograms, whereby the number of permutations of eligible supplementalprograms equals the number of different cohorts of the program cohortgroup, thereby completing step 3006. Therefore, the SP module creates anequal number of permutations of eligible supplemental programs andcohorts. Finally, after defining a plurality of different permutationsof the eligible supplemental programs for the target drug, the SP moduleassigns a different permutation of supplemental programs with eachcohort of the program cohort group, thereby completing step 3007.

According to one embodiment of the present invention, the SP modulereceives instructions regarding how to define the different permutationsof eligible supplemental programs from the administrator of the SPsystem 300. For example, the administrator of the SP system 300 maytransmit instructions to the SP module which dictate the exactconfigurations of each of the different permutations of eligiblesupplemental programs. This may be beneficial if the administrator wouldlike to test specifically the effectiveness of particular combinationsof supplemental programs on patient adherence. In such embodiments, ifthe instructions comprise the specific permutations of eligiblesupplemental programs, then the SP module may not have to determinewhich supplemental programs are eligible for the target drug, define aplurality of different permutations, and/or assign the differentpermutations to each of the cohorts.

In the preferred embodiment of the present invention, one of thepermutations of supplemental programs is created such that the cohort ofwhich it is associated is a control group. A control group is a cohortwhich is assigned a permutation of supplemental programs that eitherdoes not comprise any supplemental programs or comprises one or moresupplemental programs that are also common to all of the plurality ofpermutations of supplemental programs assigned to the other cohorts ofthe program cohort group. Stated another way, a permutation ofsupplemental programs may be used as a control group if: (1) it does notcomprise any supplemental programs; or (2) only comprises supplementalprograms that are also included in each of the other permutations ofsupplemental programs of a program cohort group. The use of a controlgroup is beneficial because it provides a baseline for the SP module toanalyze the effectiveness of the other supplemental programs on patientadherence. Nonetheless, although it is preferred that one of theplurality of cohorts is a control group, it should be noted that inalternate embodiments of the present invention a control group may beomitted.

Further, according to one embodiment of the present invention, eachcohort further comprises a current counter and a maximum counter. Themaximum counter defines/stores the maximum number of times thepermutation of supplemental programs for a cohort may be activated bythe SP module, while the current counter defines/stores the number oftimes the permutation of supplemental programs for a particular cohorthas been activated to date. Therefore, by using both a current count anda maximum counter, the SP module may ensure that the permutation ofsupplemental programs for each cohort of a program cohort group getactivated an equal number of times. As discussed in more detail below,by limiting the total number of times the SP module may activate thepermutation of supplemental programs for each cohort, each permutationof supplemental programs will have been activated the same number oftimes when the SP module determines the effectiveness of eachpermutation. This helps to provide a more accurate representation of theeffectiveness of the supplemental programs on patient adherence.Further, in one embodiment of the present invention, when the currentcounter of all the cohorts of a program cohort group reach the maximumcounter, the SP module ceases to activate the permutations ofsupplemental programs for the cohorts of the program cohort group, andanalyzes patient adherence data to determine the effectiveness of thedifferent permutations of the supplemental programs on patientadherence.

Referring to FIG. 32, a schematic diagram of a method of defining aplurality of different permutations of eligible supplemental programsfor a target drug according to one embodiment of the present inventionis illustrated. As exemplified, the SP module retrieves supplementalprogram data from the supplemental program database 303, thesupplemental program data relating to supplemental programs which areeligible for the target drug. After retrieving the supplemental programdata, the SP module defines a plurality of different permutations ofeligible supplemental programs. This may be accomplished by the rulesengine of the SP module or via instructions received by the SP modulefrom the administrator of the SP system 300, as discussed in detailabove.

Referring to FIG. 32, the permutations of supplemental programs aredefined by the SP module such that permutation number 1 does notcomprise any eligible, supplemental programs, permutation number 2comprises supplemental program number 1, permutation number 3 comprisessupplemental program number 2 and 3, and permutation number 4 comprisessupplemental program number 1 and 3. It should be noted that FIG. 32 isbut just one example of the SP module defining a plurality of differentpermutations of supplemental programs. It should be noted that thepresent invention is not limited to the number of permutations ofsupplemental programs or the number of supplemental programs perpermutation.

Referring to FIG. 33, a schematic diagram of a method of assigning adifferent permutation of eligible supplemental programs to each cohortout of a plurality of cohorts of a program cohort group according to oneembodiment of the present invention is illustrated. After creating theplurality of permutations of the eligible supplemental programs, the SPmodule assigns a different permutation of eligible supplemental programsto each cohort. According to one embodiment of the present invention,the SP module may receive instructions from the administrator of the SPsystem 300 that defines how the SP module is to assign the differentpermutations of eligible supplemental programs to each cohort. However,the invention is not so limited, and in alternate embodiments of thepresent invention, the SP module may assign the permutation ofsupplemental programs to each cohort using an algorithm stored withinthe cohort database 305 that dictates how the permutations are to beassigned to each cohort.

For example and as exemplified in FIG. 33, the central portion 301 theSP module assigns program permutation number 2 to cohort number 1,program permutation number 1 to cohort number 2, program permutationnumber 3 to cohort number 3, and program permutation number 4 to cohortnumber 4. It should be noted that this is just one non-limiting exampleof the assignment of permutations of supplemental programs to cohorts inaccordance with the present invention. Specifically, it should be notedthat the permutations of the present invention are not limited to anyspecific number of supplemental programs. Therefore, although only amaximum of two supplemental programs are exemplified in any onepermutation, in alternate embodiments of the present invention, apermutation may comprise any number of eligible supplemental programs.

As discussed in more detail below, since permutation number 1 does notcomprise any supplemental programs, cohort number 2, which was assignedpermutation number 1, is a control group. Stated another way, cohort 2(and supplemental program permutation number 1) is a control group inwhich no supplemental programs are available for the target drug. Forfurther example, it should be noted that a control group may comprise atleast one supplemental program, as long as the supplemental program(s)of the control group are also assigned to the other cohorts of theprogram cohort group.

Referring back to FIG. 30, after assigning a different permutation ofeligible supplemental programs to each of the cohorts, the SP modulestores the association of each permutation of eligible supplementalprograms with its associated cohort in the cohort database 305 of the SPsystem 300, thereby completing step 3008. Therefore, the cohort database305 comprises a correlated list of the cohorts, the assigned health careproviders 101 of each cohort, and the assigned permutation ofsupplemental programs of each cohort.

According to one embodiment of the present invention, the SP modulegenerates a program identifier for each of the different permutations ofsupplemental programs. Similar to the cohort identifier discussed above,in one embodiment of the present invention the program identifier is aunique string of numbers used by the SP module to identify thatparticular permutation of supplemental programs. After generating aprogram identifier for each of the different permutations ofsupplemental programs, the SP module associates a program identifierwith each of the plurality of health care providers 101 based on theirassociated cohort, thereby completing step 3009. Thereafter, the SPmodule stores the association in the cohort database 305 of the SPsystem 300.

Therefore, according to one embodiment of the present invention, all ofthe health care providers 101 of a particular cohort are associated withthe unique cohort identifier of their associated cohort and the uniqueprogram identifier of the associated permutation of supplementalprograms of their cohort in the cohort database 305. As a result, and asdiscussed in more detail below, the SP module may more easily identifythe associated cohort and permutation of supplemental programs of aparticular health care provider 101 using the cohort identifier and theprogram identifier stored in the cohort database 305.

Next, the SP module generates at least one cohort rule, and assigns atleast one cohort rule to each cohort of the plurality of cohorts,thereby completing step 3010. A cohort rule is similar to a rule, asdiscussed in detail above, but a cohort rule is a restriction assignedto each of the plurality of cohorts, whereas the rules discussed aboveare restrictions assigned to at least one supplemental program.Therefore, the cohort rules further restrict a cohort to additionalconstraints in addition to the target drug and provider 101 restrictionsdiscussed above. Thus, in order for a prescription to qualify for thepermutation of supplemental programs of a cohort, the prescription mustmeet the target drug, provider 101, and cohort rules of a particularcohort. After generating and assigning cohort rules to each of thecohorts of a program cohort group, the SP module stores the cohort rulesin association with each cohort in the cohort database 305.

As discussed in more detail below, the rules engine of the SP moduleapplies the cohort rule to the prescription for the target drug todetermine whether the prescription qualifies for the cohort, and thusthe permutation of supplemental programs of that cohort. Therefore,although a prescription may be for a target drug of a cohort in whichthe provider 101 belongs, the cohort may still not be eligible for thepermutation of supplemental programs of the cohort unless theprescription also meets the cohort rule(s). Thus, in such embodiments, aprescription will only be deemed eligible for a cohort if the rulesengine of the SP module determines that the prescribed substance is thetarget drug of a cohort, the provider 101 is assigned to the cohort, andthe prescription meets the cohort rules of the cohort. Nonetheless, itshould be noted that the invention is not so limited, and in alternateembodiments of the present invention, each of the plurality of cohortsmay not be assigned any cohort rules.

It should further be noted that the cohort rules are exclusionary rules,meaning that if there is an applicable cohort rule for a prescription,then other non-cohort rules (or “rules” as discussed above) are notapplied by the rules engine of the SP module when determining whetherthe prescription qualifies for the cohort, and in turn the permutationof supplemental programs of that cohort. Additionally, in one embodimentof the present invention, the cohort rules comprise the name of thetarget drug so that the SP module may more easily apply the cohort rulesto received prescription data. However, the invention is not so limited,an in alternate embodiments of the present invention, the SP module mayapply both the cohort rules and non-conflicting non-cohort rules.

A cohort rule may be similar to any of the non-cohort rules discussedabove. For further example, a cohort rule may relate to the dosagestrength of the substance (e.g., the prescription of the target drugmust be for 60 mg pills or the prescription of the target drug must beequal to or greater than 30 mg pills), the duration in which the patienthas been receiving prescriptions for the target drug (e.g., the patientmust have been prescribed the drug for at least 90 days prior to thecurrent prescription), the age of the patient (e.g., the prescriptionmust be for a patient who is greater than 18 years old or a patient whois less than or equal to 60 years old), the Medication Persistency Rate(MPR) of the patient, or any other patient adherence data.

Similar to the set-up of the permutations of supplemental programs,according to one embodiment of the present invention, the SP modulereceives instruction from an administrator of the SP system relating tothe generation of the cohort rules of a plurality of cohorts. Forexample, the administrator of the SP system 300 may transmitinstructions to the SP module which dictate the exact cohort rules forthe plurality of cohorts. This may be beneficial if the administratorwould like to specifically test the effectiveness of supplementalprograms on a particular patient type, patients at a particular usagestage of the target drug, or prescriptions for a particular strength ofthe target drug. However, in an alternate embodiment of the presentinvention, the rules engine of the SP module generates the cohort rulessuch that each of the plurality of cohorts are configured to beactivated for the most common types of patients receiving prescriptionsfor the target drug or for patients with a specific MPR range (e.g.patients who have an MPR between 30%-80%).

In accordance with one embodiment of the present invention, the cohortrules may be reconfigured or altered by the SP module at any time. Forexample, the administrator of the SP system 300 may determine that theresults being received from a particular cohort are not ideal.Therefore, the administrator may remove, alter, or reconfigure anycohort rules at any stage after the cohorts are created. By allowing theadministrator to alter the cohort rules after the cohorts are in use,the SP module enables the administrator to correct or alter thequalifications required for each cohort. For instance, in oneembodiment, the SP module may allow an administrator to use a slidingscale to adjust the range of a particular cohort rule (e.g., a cohortrules restriction qualification of the cohort to prescriptions whosepatients have an MPR in a certain range).

Further, in another embodiment of the present invention, the SP modulemay comprise an algorithm that is configured to automatically adjust acohort rule based on a percentage of prescription that pass or fail thecohort rule. For example, the SP module may automatically adjust acohort rules restriction qualification of the cohort to prescriptionswhose patients have an MPR between 40-80% to an MPR between 30-90% inorder to increase the number of prescriptions qualifying for the cohort.

Further, according to one embodiment of the present invention, one ormore cohort rules may be used by the SP module to define the target drugof each cohort, select and allocate providers 101 for each cohort,define the maximum counter of each cohort, and/or select and allocatethe permutation of supplemental programs for each cohort. In suchinstances, the SP module may not receive instructions from theadministrator of the SP system 300 that define how to assign providers101 between cohorts and/or select and allocate the permutation ofsupplemental programs for each cohort. For example, instead of receivinginstructions relating to the specific assignment of providers 101between cohorts, the SP module may receive instructions defining acohort rule that automatically allocates specific permutations ofsupplemental programs to specific providers (e.g., providers living in acertain geographic location are allocated a particular permutation ofsupplemental programs for a particular prescribed substance(s)).Therefore, in such embodiments, the cohorts will be automaticallydefined and created by the SP module using cohort rules.

Still referring to FIG. 30 and as discussed above, the SP module storesa correlated list of the information relating to cohorts in the cohortdatabase 305 to aid the SP module in performing additional processingsteps. In step 3011, the SP module stores the cohort information in acohort relation table created by the SP module, the cohort relationtable being stored by the SP module in the cohort database 305 of the SPsystem 300. The cohort relation table associates or links a plurality ofdata relating to each cohort. For example, the cohort relation table mayassociate or link any combination of the data relating to each cohort,such as but not limited to, the cohort identifier of a cohort, theprovider NPI numbers of a cohort, the target drug of a cohort, thepermutation of supplemental programs of a cohort, the current andmaximum counter of a cohort and/or the cohort rules of a cohort.Therefore, when the SP module receives prescription data, the rulesengine may use the cohort relation table to determine whether a cohortis applicable to the received prescription data, the associatedsupplemental programs of a cohort, and the current and maximum counterof a cohort.

Referring to FIG. 34, a cohort relation table 3400 according to oneembodiment of the present invention is illustrated. As discussed above,according to one embodiment of the present invention, the cohortdatabase 305 stores a cross-referenced listing of cohort identifiers,health care provider NPI numbers, target drug(s), permutation ofsupplemental programs, current/maximum counter, and cohort rules.Nonetheless, it should be noted that the cohort relation table maycomprise a cross-referencing of any number of cohort related data items.Further, it should be noted that the information listed in the cohortrelation table 3400 is generically illustrated for purposes ofsimplicity.

The cohort relation table 3400 may be utilized by the SP module whencross-referencing the cohort database 305, such that thecross-referencing is accomplished using the cohort relation table 3400.This enables the SP module to determine whether a health care provider101 is associated with a cohort, and if so, what specific cohort, whatpermutation of supplemental programs associated with the cohort, etc.the SP module should apply for an electronic prescription.

Although exemplified as a single table, it should be noted that inalternate embodiments of the present invention, the cohort relationtable may consist of multiple separate tables that are linked to oneanother (e.g., mapping tables). Therefore, the SP module may determineassociated data of one element (e.g., a cohort, a health care provider101, a target drug, etc.) by searching through the appropriate mappingtables stored within the cohort database 305 of the SP system 300.

Further, in accordance with one embodiment of the present invention, theSP module may change a provider 101 between cohorts using the cohortrelation table. Therefore, the SP module may move providers 101 betweencohorts, and such changes would update their cohort association storedwithin the cohort relation table in the cohort database 305.

After storing the cohort relation table in the cohort database 305, theSP module has defined the plurality of cohorts of a program cohortgroup.

2. Receiving Data Relating to an Electronic Prescription and Activatingthe Supplemental Programs Associated with the Health Care Provider'sCohort

After a plurality of cohorts is defined by the SP module, the SP moduleis ready to analyze the effectiveness of the different permutations ofsupplemental programs on patient adherence for the target drug. However,the first step is for the SP module to activate the permutation ofsupplemental programs of each of the cohorts for electronicprescriptions. As discussed in more detail below, the SP module receivesinformation relating to an electronic prescription for the target drugwritten by one of the health care providers 101, determines whether thehealth care provider 101 is part of an existing cohort, and activatesthat provider's permutation of supplemental programs for the patientupon the provider's request. Thereafter, the SP module receives patientadherence data and analyzes the effectiveness of the activatedsupplemental programs on the patient's adherence to the target drug. Itshould be noted, as discussed above, that the target drug may be justone or a plurality of prescribed substances as indicated by the targetdrug data.

Referring to FIGS. 35a -35 b, a flow chart of a method 3500 forreceiving data relating to an electronic prescription for the targetdrug and activating the permutation of supplemental programs associatedwith the health care provider's cohort for the target drug according toone embodiment of the present invention is illustrated. It should benoted that the method 3500 of FIGS. 35a-35b may be considered anintervening method that works in conjunction with the method 800exemplified in FIGS. 8a -8 c. For example, according to one embodimentof the present invention, the method 3500 picks up after the health careprovider 101 writes an electronic prescription for a prescribedsubstance using the thin client portion 203 of the EP module and the SPwidget 302 retrieves data relating to the electronic prescription fromthe thin-client portion of the EP module 203. Therefore, the method 3500begins with the central portion 301 of the SP module receiving datarelating to the electronic prescription of the prescribed substance forthe patient, similar to as discussed above with respect to step 801 ofFIG. 8a , thereby completing step 3501.

Further, it should be noted that the method 3500 occurs after theperformance of method 3000 by the SP module. Finally, as discussed abovewith respect to the method 800, the method 3500 is not a one-timetransmission of information, but rather a recurrent process that occurseach time a health care provider 101 writes and/or transmits anelectronic prescription.

After receiving the electronic prescription data, the SP module extractsthe NPI number of the health care provider 101 who wrote theprescription and the prescribed substance of the electronic prescriptionfrom the received electronic prescription data, thereby completing step3502. As noted above, the electronic prescription data comprises firstpatient data that is specific to the patient, first prescribed substancedata that is specific to the prescribed substance, first provider datathat is specific to the health care provider 101, and first payor datathat is

Next, the central portion 301 of the SP module determines whether theprescribed substance of the electronic prescription is part of aparticular cohort in decision step 3503. According to one embodiment ofthe present invention, the central portion 301 of the SP modulecross-references the prescribed substance data from the electronicprescription with cohort relation table stored in the cohort database305 of the SP system 300 to determine if the prescribed substance of theelectronic prescription is the target drug of one or more cohorts. Forexample, according to one embodiment of the present invention, the SPmodule determines whether the target drug name is associated with any ofthe defined cohorts.

If the prescribed substance is not associated with any cohorts, then themethod moves to step 3504, and as a result, returns to step 802 in FIG.8a . In such instances, the prescribed substance is not associated withany cohorts and, therefore the method returns to step 802 of FIG. 8a .Nonetheless, the SP module may still determine eligible supplementalprograms for the patient based on the received electronic prescriptiondata, as discussed above in detail with respect to FIGS. 8a -8 b.However, if the prescribed substance is the same as the (or a) targetdrug of one or more cohorts, then the method continues to step 3505.

Thereafter, the SP module determines whether the health care provider101 who wrote the prescription is part of one of the cohorts identifiedin decision step 3505. According to one embodiment of the presentinvention, the SP module cross-references the provider data from theelectronic prescription with the cohort database 305 of the SP system300 to determine if the provider 101 has an associated cohort, andfurther if the target drug of the associated cohort is the same as theprescribed substance. For example, in one embodiment of the presentinvention, the SP module determines whether the provider's NPI number isassociated with any of the cohorts for the target drug.

If the health care provider 101 is not associated with any cohorts, thenthe method moves to step 3506, and as a result, returns to step 802 inFIG. 8a . In such instances, even though the prescribed substance is thetarget drug of one or more cohorts, the provider 101 is not associatedwith any of the cohorts of that target drug, and therefore the cohort(s)of the target drug are not relevant for determining supplementalprograms. Nonetheless, the SP module may still determine eligiblesupplemental programs for the patient based on the received electronicprescription data, as discussed above in detail with respect to FIGS. 8a-8 b. However, if the health care provider 101 is associated with acohort of the prescribed substance, then the process continues on tostep 3507.

If the method continues to step 3507, then the health care provider 101is associated with at least one cohort and the prescribed substance isthe (or a) target drug of the provider's associated cohort. At thatpoint, the rules engine of the SP module retrieves the cohort rules forthat cohort from the cohort relation table stored within the cohortdatabase 305. As noted above, the cohort rules define rules orrestrictions that are used by the rules engine to determine whether ornot the electronic prescription is eligible for the cohort, and in turnthe permutation of supplemental programs of the cohort. It should benoted that in accordance with one embodiment of the present invention,the rules engine of the SP module further retrieves patient data,prescribed substance data, provider data, and/or payor data from therecords database 304 of the SP module. This is similar to as discussedwith reference to steps 802-805 of FIG. 8 a.

Referring to FIG. 35b , at step 3508 the rules engine of the SP moduledetermines whether the received (and potentially retrieved) data meetsthe cohort rules of the provider's cohort. If the received/retrieveddata does not meet the cohort rules, then the method moves to step 3509and returns to step 802 of FIG. 8a . In such instances, even though theprovider 101 is a part of a cohort and the prescribed substance is thetarget drug of that cohort, the electronic prescription does not meetthe other requirements, or cohort rules, of that cohort. Therefore, theelectronic prescription is not eligible for the permutation ofsupplemental programs for that cohort.

However, if the received/retrieved data does meet the cohort rules, thenelectronic prescription is eligible for the cohort and the methodcontinues to step 3510. At step 3510, the SP module determines whetherthe current counter of the permutation of supplemental programs meets orexceeds the maximum counter of the permutation of supplemental programs.The SP module makes the determination by checking the cohort relationtable stored within the cohort database 305. If the current counter doesmeet or exceed the maximum counter of the permutation of supplementalprograms, then the method continues to step 3511 and returns to step 802in FIG. 8a . In such instances, even though the provider 101 is a partof a cohort, the prescribed substance is the target drug of that cohort,and the electronic prescription meets the cohort rules of that cohort,the permutation of supplemental programs for that cohort has been met orexceeded, so the SP module will not continue to activate thatpermutation of supplemental programs. However, if the current counterdoes not meet or exceed the maximum counter of the permutation ofsupplemental programs, then the method continues to step 3512. Further,it should be noted that in embodiments when the cohort does not comprisea current and maximum counter for the permutation of supplementalprograms, steps 3510 and 3511 may be omitted.

At step 3512, the SP module retrieves the permutation of supplementalprograms associated with the provider's cohort from the cohort database305. According to one embodiment of the present invention, the SP moduleretrieves the cohort identifier of the provider's cohort from the cohortdatabase 305, and in turn, using the cohort identifier, retrieves theprogram identifier of the cohort from the cohort database 305. Theprogram identifier identifying each of the supplemental programs of thepermutation of supplemental programs associated with the provider'scohort.

After retrieving the permutation of supplemental programs from thecohort database 305, the SP module retrieves data relating to each ofthe supplemental programs associated with the permutation ofsupplemental programs, thereby completing step 3513. Next, the methodcontinues to step 3514, and as a result, returns to step 809 in FIG. 8a. Thereafter, the method may continue as discussed above with referenceto FIGS. 8a -8 c. The method may include, but not limited to, any of theembodiments described above.

Therefore, according to one embodiment of the present invention and asdiscussed in greater detail above, the SP module generates and displaysa GUI comprising a list of the supplemental programs associated with theprovider's cohort on the display device 121 for the provider's input.Therefore, each of the supplemental programs of the permutation ofsupplemental programs associated with the cohort to which the healthcare provider 101 belongs is displayed to the health care provider 101for selection and activation. Also similar to as discussed above, the SPmodule will activate each of the supplemental programs associated withthe cohort to which the health care provider 101 belongs that areselected and activated by the health care provider 101 using the inputdevice 122 of the HCP system 100. As noted above, activation of asupplemental program may comprise many different steps, including, butnot limited to, the delivery or transmission of content to the patient,the transmitting of patient information to sign a patient up for aservice, or any other form as discussed above in detail.

However, the invention is not so limited and according to one embodimentof the present invention, and unlike as described above, the provider101 does not have the opportunity to select or de-select thesupplemental programs. Rather, since the provider 101 is associated withthe particular cohort, all of the supplemental programs associated withthat cohort are automatically activated by the SP module. In suchembodiments, a GUI may be, but is not necessarily, displayed to theprovider 101 via the display device 121. The supplemental programs aresimply activated by the SP module for the patient.

It should be noted that among the processes discussed above that may beincorporated into the embodiments where the prescribing health careprovider 101 is a part of a cohort, the use of delivery modes may beincorporated into herein. For example, in one embodiment of the presentinvention the SP module may retrieve delivery mode data relating to thepatient and the supplemental programs of the cohort from the recorddatabase 304 and supplemental program database 303 respectively, asdiscussed in detail above. Thereafter, the SP module may comparedelivery mode data relating to the patient with the delivery mode datarelating to the supplemental programs to determine common deliverymodes, and displaying the common delivery modes of the supplementalprograms in the GUI via the display device 121 for selection andacceptance by the health care provider 101, as also discussed above ingreater detail. Finally, in such embodiments, if activation of asupplemental program of the cohort causes content to be delivered to thepatient, the delivery of the content is via the delivery mode that isselected and accepted by the health care provider 101.

Furthermore, it should be noted that in alternate embodiments of thepresent invention the SP module widget 302 and not the central portion301 of the SP module performs the processes relating to the use of theplurality of cohorts. For example, in one embodiment of the presentinvention, the SP module widget 302 and not the central portion 301 ofthe SP module determines whether the provider 101 is a part of aparticular cohort and/or whether the prescribed substance of theelectronic prescription is the (or a) target drug of the provider'sassociated cohort. In such embodiments, the SP module widget 302 maytrack electronic prescriptions being prescribed by each one of theplurality of health care providers 101 that are part of one of theplurality of cohorts. Similar to above, the SP module widget 302 maycross-reference electronic prescription data with the cohort database305. In such embodiments, the cohort database 305 may reside within thememory 113 of the HCP system 100. Thereafter, when a health careprovider 101 out of the plurality of health care providers 101 that is apart of one of the plurality of cohorts writes an electronicprescription for the (or a) target drug of that cohort, the SP modulewidget 302 retrieves electronic prescription data for the target drugfrom the thin-client portion of the EP module 203 and transmits theelectronic prescription data for the target drug to the central portion301 of the SP module.

Generally, it should be noted that since each cohort is assigned adifferent permutation of supplemental programs, each cohort may be usedto analyze the effectiveness of a specific permutation of supplementalprograms on patient adherence. Stated another way, and as discussed inmore detail below, each of the plurality of cohorts analyzes theeffectiveness of its assigned supplemental programs on patient adherencefor the prescribed substance(s) identified by the target drug data.

2a. Alternate Embodiment of Processing a Prescription to DetermineEligible Supplemental Programs Via Cohorts

Referring to FIG. 36a , a flow chart of a method 3600 of retrievingsupplemental program data in accordance with an alternate embodiment ofthe present invention is illustrated. Referring to FIG. 36b , a method3600 of generating a document list of all eligible supplemental programsthat are selected and accepted by a provider 101 for an electronicprescription according to one embodiment of the present invention isillustrated. Referring to FIG. 36c , a method 3600 of retrieving thedocument associated with supplemental programs that are selected andaccepted by a provider 101 for an electronic prescription according toone embodiment of the present invention is illustrated.

It should be noted that the method 3600 is an alternate method to method3500 discussed in reference to FIGS. 35a-35b above. Specifically, asopposed to the method 3500, in which the rules engine first determineswhether the electronic prescription is eligible for a supplementalprogram prior to determining if there are any eligible supplementalprograms, in the method 3600 the rules engine first determines if thereare any supplemental programs for which the electronic prescription iseligible, and then subsequently determines whether any of the eligiblesupplemental programs are part of a predefined cohort of the provider101. It should be further noted that in alternate embodiments of thepresent invention, the SP module may perform a combination of any of thesteps of methods 3500 and 3600 when determining eligible supplementalprograms for cohort related electronic prescriptions.

Further, it should be noted that steps 3601-3631 are performed by therules engine of the SP module, while steps 3632-3634 are performed bythe central portion 301 of the SP module. Therefore, although theprocess of steps 3601-3631 is discussed with reference to the “SPmodule,” it should be noted that the steps 3601-3631 are performed bythe rules engine of the SP module. Nonetheless, the invention is not solimited and according to other embodiments of the present invention, thecentral portion 301 of the SP module and/or the rules engine may performany of the steps 3601-3634 discussed below.

The method begins at step 3601 with the SP module storing receivedelectronic prescription data in the memory 313 of the SP system 300.According to one embodiment of the present invention, the electronicprescription data may be stored in the record database 304. However, itshould be noted that in other embodiments of the present invention, theelectronic prescription data may be stored in its own database or intemporary memory within the SP system 300.

After storing the electronic prescription data, the SP module transmitsthe electronic prescription data to the rules engine for evaluation,thereby completing step 3602. Next, the rules engine evaluates theelectronic prescription data to determine if there are any eligiblesupplemental programs out of the plurality available supplementalprograms for the electronic prescription, thereby completing step 3603.If there are no eligible supplemental programs for the prescription,then an empty response is returned in step 3604, and the method ends.However, if there is at least one eligible supplemental programreturned, then the method continues to step 3605.

At step 3605, the SP module stores, in a failed programs log in therecord database 304, a listing of all of the supplemental programs ofthe target drug for which the electronic prescription was not eligible.For example, if the prescribed substance met the rules for thesupplemental program, but the provider 101 or dosage of the substancedid not meet the rules of the supplemental program, then thatinformation is stored within the failed programs log. By storing all ofthe ineligible supplemental programs for each received prescription, thefailed programs log provides a means by which the administrator of theSP system 300 may analyze why certain supplemental programs are beingactivated more or less than others. This is beneficial in determininghow to increase or decrease the activation of certain supplementalprograms.

Thereafter, the SP module processes each eligible supplemental program,preferably one at a time, in step 3606. First, at decision step 3607,the rule engine of the SP module determines whether the supplementalprogram is cohort related. According to one embodiment, the SP modulecross references the program identifier of the supplemental program withthe cohort relation table (or mapping tables) stored within the cohortdatabase 305. This is beneficial if some of the supplemental programsreturned by the rule engine in step 3603 are cohort related while othersare not.

If the returned supplemental program is not cohort related (i.e., theprovider 101 and/or the substance is not part of the same cohort, or thecohort rules are not met), then the method 3600 continues to step 3610.However, if the supplemental program is cohort related, then the methodcontinues to step 3608. At step 3608, the rules engine of the SP modulesearches for the provider's cohort using the supplemental programidentifier and the NPI number of the provider 101. Specifically, therules engine cross-references the cohort relation table (or mappingtables) stored within the cohort database 305 to determine the specificcohort in which the supplemental program and electronic prescriptionbelong.

Upon determining the provider's cohort for the substance of theelectronic prescription, the rules engine of the SP module determineswhether the provider's cohort is a control cohort (or control group),thereby completing decision step 3609. As discussed above, a controlgroup is a cohort which is assigned a permutation of supplementalprograms that either does not comprise any supplemental programs orcomprises one or more supplemental programs that are also common to allof the plurality of permutations of supplemental programs of the otherrelated plurality of cohorts. If the provider's cohort is a controlgroup, then the method continues to step 3614, and a program option forthe eligible supplemental program is not generated for display to theprovider 101. However, if the provider's cohort is not the controlgroup, then the method continues to step 3610.

Nonetheless, it should be noted that in some embodiments of the presentinvention, the method may continue to step 3610 although the provider'scohort is the control group. Specifically, this may be the case if theprovider's control group is assigned a plurality of supplementalprograms that are common to all of the plurality of permutations ofsupplemental programs assigned to each of the other cohorts of theprogram cohort group. In such instances, it is important that thesupplemental programs assigned to the control group are also activated.Therefore, in such instance, the method may continue to step 3610.

At step 3610, the rules engine of the SP module retrieves the programcohort group of the provider's cohort, which may comprise a currentcounter and a max counter of the cohort, from the cohort database 305 ofthe SP system 300. After retrieving the program cohort group (and thecurrent and max counter of the supplemental program for the provider'scohort), the SP module determines whether activation of the supplementalprogram is controlled by the provider's cohort in decision step 3611. Itshould be noted that one method of controlling the activation of asupplemental program is through the use of a current and max counter. Ifthe activation of the supplemental program is not controlled by acurrent and max counter (e.g., the supplemental program is not relatedto a cohort, or the provider's cohort does not comprise a correspondingmax counter for the supplemental program), then the method continues tostep 3613. However, if the activation of the supplemental program iscontrolled by the current and max counter, then the method continues tostep 3612.

At decision step 3612, the SP module determines whether the currentcounter of the supplemental program for the provider's cohort is greaterthan or equal to the maximum counter of the supplemental program for theprovider's cohort. If the current counter is greater than or equal tothe maximum counter, then the supplemental program has been activatedits allotted amount of times for the particular cohort, and as such, themethod continues to step 3614. At step 3614, the SP module skips thesupplemental program such that the eligible supplemental program is notactivated. However, if the current counter is less than the maximumcounter, then the supplemental program has not been activated itsallotted amount of times for the particular cohort, and as such, themethod continues to step 3613.

At step 3613, the SP module generates a supplemental program option forthe supplemental program in a response. As discussed below withreference to FIG. 36b , the response will be transmitted by the centralportion 301 of the SP module to the SP widget 302 residing on the HCPsystem 100 so that the SP module may receive the provider's selectionand activation of the eligible supplemental programs. According to oneembodiment of the present invention, a response is a pop-up window 1010,such as that exemplified in FIG. 15, and the supplemental program optionis the information relating to the eligible supplemental program option1012 display in the pop-up window 1010 on the display device 121 to theprovider 101 for the provider's selection and acceptance of eacheligible supplemental program. It should be noted that the pop-up window1010 and the information relating to the eligible supplemental program1012 is but just one non-limiting example of a response for thesupplemental program in accordance with the present invention.

It should be noted that the response may comprise information relatingto supplemental programs that are part of the provider's cohort, alongwith information relating to supplemental programs that are not part ofthe provider's cohort. However, in one embodiment of the presentinvention, the SP module removes from the response the informationrelating to all non-cohort relating supplemental programs so that onlythose supplemental programs that are part of the provider's cohort aredisplayed to the provider 101.

After generating the supplemental program option in the response, the SPmodule continues to decision step 3615. At decision step 3615, the SPmodule determines whether the any more eligible supplemental programsremaining to be processed at step 3606. In one embodiment, thisdetermination is made by the SP module through a cross-referencing ofthe supplemental programs determined to be eligible by the rules enginein step 3603. If there remains additional eligible supplemental programsthat need to be processed through steps 3606-3615, then the methodreturns to step 3606 and another eligible supplemental program isprocessed. After all of the supplemental programs determined by therules engine in step 3603 to be eligible have been processed throughstep 3606-3615, the method of FIG. 36a is complete.

Referring to FIG. 36b , a method 3600 of generating a document list ofall eligible supplemental programs that are selected and accepted by aprovider 101 for an electronic prescription according to one embodimentof the present invention is illustrated. It should be noted that themethod of FIG. 36b is a continuation of the method of FIG. 36a .Therefore, as illustrated, the method 3600 of FIG. 36b begins with step3616. It should be noted that between step 3615 and step 3616, thecentral portion 301 of the SP module has transmitted the responsecomprising the information relating to the eligible supplementalprograms to the SP widget 302, the SP widget 302 has displayed a list ofthe eligible supplemental programs on the display device 121 to theprovider 101, the provider 101 has selected and accepted the eligiblesupplemental programs they would like to activate for the patient, andthe SP widget 302 has generated a signal indicating the supplementalprograms that were both selected and accepted by the provider 101.

At step 3616, the SP module receives a signal from the SP widget 320indicating which of the supplemental programs are both selected andaccepted by the provider 101. In one embodiment, the signal may be theactivation signal as discussed above with reference to FIGS. 8a -8 c.Next, at step 3617, the SP module retrieves the list of eligiblesupplemental programs that were displayed for the provider's selectionand acceptance. The submitted program list comprising the informationrelating to each of the eligible supplemental programs, regardless ofwhether the supplemental programs were selected and accepted by theprovider 101 for activation.

Thereafter, at decision step 3618, the SP module determines whetherthere are any supplemental programs that remain to be processed by theSP module. If so, then the SP module selects one supplemental programfrom the supplemental program list and determines whether the signalreceived from the SP widget 302 indicates that the supplemental programwas selected and accepted by the provider 101. If the supplementalprogram was not selected and accepted by the provider 101, then themethod continues to step 3620 and the supplemental program does not getactivated. However, if the supplemental program was selected andaccepted by the provider 101, then the method continues to step 3621.

It should be noted that the process of steps 3621-3623 is very similarto the process of steps 3607-3609 discussed above with respect to FIG.36a . At decision step 3621, the SP module determines whether thesupplemental program is cohort related. As noted above, in oneembodiment, the SP module cross references the program identifier of thesupplemental program with the cohort relation table (or mapping tables)stored within the cohort database 305. Further, it should be noted thatin one embodiment of the present invention, steps 3621-3623 are omitted.In such embodiments, the method goes from step 3620 directly to step3624.

If the supplemental program is not cohort related, then the methodcontinues to step 3624. However, if the supplemental program is cohortrelated, then the method continues to step 3622. At step 3622, the rulesengine of the SP module searches for the provider's cohort using thesupplemental program identifier and the NPI number of the provider 101.Specifically, the rules engine cross-references the cohort relationtable (or mapping tables) stored within the cohort database 305 todetermine the specific cohort in which the supplemental program andelectronic prescription belong.

Upon determining the provider's cohort, the rules engine of the SPmodule determines whether the provider's cohort is a control cohort (orcontrol group), thereby completing decision step 3623. If the provider'scohort is a control group, then the method continues to step 3620, andthe eligible supplemental program is not activated. However, if theprovider's cohort is not the control group, then the method continues tostep 3624.

Nonetheless, similar to as discussed above, in some embodiments of thepresent invention, the method may continue to step 3624 although theprovider's cohort is the control group. Specifically, this may be thecase if the provider's control group is assigned a plurality ofsupplemental programs that are common to all of the plurality ofpermutations of supplemental programs assigned to each of the othercohorts of the program cohort group. In such instances, it is importantthat the supplemental programs assigned to the control group are alsoactivated. Therefore, in such instance, the method may continue to step3624.

At step 3624, the rules engine of the SP module retrieves the programcohort group of the provider's cohort, which may comprise a currentcounter and a max counter of the cohort, from the cohort database 305 ofthe SP system 300. After retrieving the program cohort group (and thecurrent and max counter of the supplemental program for the provider'scohort), the SP module determines whether activation of the supplementalprogram is controlled by the provider's cohort in decision step 3625. Ifthe activation of the supplemental program is not controlled by acurrent and max counter, then the method continues to step 3627.However, if the activation of the supplemental program is controlled bythe current and max counter, then the method continues to step 3626.

At decision step 3626, the SP module determines whether the currentcounter of the supplemental program for the provider's cohort is greaterthan or equal to the maximum counter of the supplemental program for theprovider's cohort. If the current counter is greater than or equal tothe maximum counter, then the supplemental program has been activatedits allotted amount of times for the particular cohort, and as such, themethod continues to step 3620. At step 3620, the SP module skips thesupplemental program such that the eligible supplemental program is notactivated. However, if the current counter is less than the maximumcounter, then the supplemental program has not been activated itsallotted amount of times for the particular cohort, and as such, themethod continues to step 3627.

At step 3627, the SP module retrieves the service configuration from thesupplemental program database 303 for calling a third party programvendor 400. The service configuration comprises information relating tothe specific third party program vendor 400 that comprises thesupplemental program. As noted above, in accordance with one embodimentof the present invention, the SP module does not store the physicaldocuments or run the services that are the supplemental programs.Rather, the SP module simply stores information relating to thesupplemental programs so that upon activation, the SP module mayretrieve the actual document from the appropriate third party programvendor 400 or enroll the patient in the service by transmitting patientdata to the appropriate third party program vendor 400. Nonetheless, inone embodiment of the present invention, the SP module does store theactual documents and run the actual services that are the supplementalprograms. In such embodiments, steps 3627-3629 may be omitted.

Next, at step 3628, the SP module transmits a signal to the appropriatethird party program vendor 400 to invoke the vendor 400 to confirm thatthe third part program vendor 400 does in fact have stored the actualdocument or service relating to the supplemental program. Thereafter,the SP module receives the confirmation signal from the appropriatethird party program vendor 400, and logs the confirmation from the thirdparty program vendor 400 in a log table at step 3629, the log tablebeing stored within the cohort database 305.

Next, at step 3630, the SP module generates the supplemental programtitle and puts the supplemental program title in a response list, theresponse list stored in the cohort database 305. As discussed in moredetail below, the response list comprises the titles of the supplementalprograms that were selected and accepted by the provider 101. Afterputting the document title in the response list, the method returns tosteps 3617 and 3618 and the SP module determines if there are anyremaining supplemental programs that need to be processed. Upon the SPmodule processing each of the selected and accepted supplementalprograms, the method continues to step 3631 and the SP module generatesa response, the response comprising the response list that comprises thetitles of the supplemental programs that were selected and accepted bythe provider 101.

Referring to FIG. 36c , a method 3600 of retrieving the documentassociated with supplemental programs that are selected and accepted bya provider 101 for an electronic prescription according to oneembodiment of the present invention is illustrated. It should be notedthat the method of FIG. 36c is a continuation of the method of FIG. 36b.

At step 3632, the central portion 301 of the SP module receives arequest from the rules engine which comprises the response listing a logidentifier for the supplemental programs that were selected and acceptedby the provider 101 for activation. The log identifier has the programidentifiers for the supplemental programs that were selected andaccepted by the health care provider 101.

Next, in step 3633, the central portion 301 of the SP module retrievesthe supplemental program service log from one or more of the databasesof the SP system 300. The supplemental program service log indicates thesupplemental programs that were selected and accepted by the provider101 for activation.

Next, at decision step 3634, the central portion 301 of the SP moduledetermines whether the supplemental program is related to the provider'scohort. If the supplemental program is cohort related, then the methodcontinues to step 3635 and the central portion 301 of the SP moduleretrieves the program group of the supplemental program, which comprisesthe current and maximum counter. However, if the supplemental program isnot cohort related, then the method continues to step 3639, as discussedin more detail below.

Assuming the supplemental program is cohort related and after retrievingthe current and maximum counter of the supplemental program for theprovider's cohort, the central portion 301 of the SP module determineswhether the current counter is less than the maximum counter at decisionstep 3636. If the current counter is not less than the maximum counter,then the central portion 301 of the SP module generates a messageindicating that the supplemental program is not available for activation(e.g., “No Coupon Available”), and includes that message in a responsethat is transmitted to the SP widget 302 for display to the provider 101on the display device 121. However, if the current count is less thanthe maximum counter, then the central portion 301 of the SP moduleincreases the current counter by one, such increase being stored in thecohort database 305, thereby completing step 3637.

Next, the central portion 301 of the SP module calls the appropriatethird party program vendor 400 and retrieves the actual document orinformation relating to the service of the supplemental program. In oneembodiment, the central portion 301 of the SP module transmits theprogram identifier to the third party program vendor 400 and receivesthe actual document or information relating to the service of thesupplemental program from the third party program vendor 400. However,the invention is not so limited, and in alternate embodiments thecentral portion 301 of the SP module may transmits any signal indicatingthe specific supplemental program to the appropriate third party programvendor 400.

Referring back to step 3634, if the supplemental program is not cohortrelated, then the central portion 301 of the SP module calls theappropriate third party program vendor 400 and retrieves the actualdocument or information relating to the service of the supplementalprogram, thereby completing step 3639. This is similar to the processdescribed with respect to step 3638.

Thereafter, the SP module receives the actual document or informationrelating to the service of the supplemental program from the appropriatethird party program vendor 400, and stores the actual document orinformation relating to the service of the supplemental program in thesupplemental program database 303 (or other temporary memory). Thus, theSP module has, within one or more of its databases, the actual documentor information relating to the service of the supplemental program.Thereafter, the SP module logs the response from the third party programvendor 400 in a log table at step 3640, the log table being storedwithin the cohort database 305.

Next, the central portion 301 of the SP module generates a response thatcomprises the actual document or information relating to the service ofthe supplemental program. It should be noted that the response maycomprise more than one document or other supplemental program relatedinformation. Thereafter, the central portion 301 of the SP moduletransmits the response, along with the associated documents andinformation, to the SP widget 302, thereby completing step 3643.

Upon receiving the response, the SP widget 302 may display a GUI to theprovider 101 that allows the provider 101 to distribute the document orother supplemental program information to the patient. In an alternateembodiment of the present invention, the SP widget 302 may transmit thedocuments directly to a printer without requiring provider interaction.Nonetheless, it should be noted that, upon receiving the response, theSP widget 302 may cause the documents and other information to bedisseminated in any manner consistent with the present invention.

3. Receiving Patient Adherence Data

After the SP module activates the supplemental programs of the cohortthat were selected and accepted by the provider 101, the patientreceives the activated supplemental programs. Thereafter, as discussedin detail below, the SP module receives patient adherence data relatingto the electronic prescription. It should be noted that since there area plurality of different cohorts and since each cohort comprises asub-set of health care providers 101, the SP module will receive patientadherence data relating to a plurality of difference electronicprescriptions generated by different health care providers 101, some ofthese prescriptions for a target drug of a cohort and other not.Further, the SP module will be reaching patient adherence data while theprogram cohort groups are still active. Thereafter, upon receivingpatient adherence data, the SP module must parse the patient adherencedata by the cohort in which the patient adherence data relates.

As noted above, according to one embodiment of the present invention,the memory 313 of the SP system 300 further comprises a patientadherence generation module 306. The SP system 300, and moreparticularly the patient adherence generation module 306, receivespatient medication history data relating to a plurality of electronicprescriptions for which supplemental programs were previously activated.It should be noted that the received patient medication history may, butdoes not have to, relate to prescriptions that met all of the cohortrules and caused the activation of the permutation of supplementalprograms for a cohort. Stated another way, the patient adherencegeneration module 306 receives patient medication history data relatingto a plurality of electronic prescriptions, regardless of whethersupplemental programs of a cohort (as opposed to supplemental programsin general) were activated for the prescription. As discussed in moredetail below, the patient adherence generation module 306 receives thepatient medication history data from another system, such as but notlimited to the pharmacy system 500 and the payor system 600.

Generally, the patient medication history data comprises informationrelating to the medication history of the patient for one or moreprescribed substances. This may, but does not necessarily, includeprescriptions for the target drug of a cohort. For example, patientmedication history may comprise any of the substance data describedabove (e.g. substance details such as the dosage, strength, form,duration, quantity, date, and refills) with reference to a prescription,the prescription start date and stop date, information relating towhether the patient picked up the prescription, the duration in whichthe prescription sat at the pharmacy prior to patient pickup, the numberof refills of the prescription that the patient filled, and the timeframe between refills in comparison to the duration of eachprescription. Further, it should be noted that the patient medicationhistory data may comprise information relating to any number ofprescriptions for any number of patients, regardless of whethersupplemental programs were activated by the SP module for thoseprescriptions.

However, in one embodiment of the present invention, the patientadherence generation module 306 only receives patient medication historydata for prescriptions in which supplemental programs were activated.Further, in other embodiments, the patient adherence generation module306 only receives patient medication history data for prescriptions of atarget drug of a cohort in which the permutation of supplemental programof that cohort were activated.

After receiving the patient medication history data, the patientadherence generation module 306 generates patient adherence data fromthe received patient medication history data. After generating thepatient adherence data, the patient adherence generation module 306stores the patient adherence data in the patient adherence database 307.According to one embodiment of the present invention, the patientadherence generation module 306 generates the patient adherence data byapplying the received patient medication history data to one or morealgorithms configured to determine patient adherence metrics from thereceived patient medication history data. Through use of the algorithms,the patient adherence generation module 306 generates one or moreadherence analytics for a particular prescription and/or medicationhistory data of a patient. In such embodiments, the algorithms arestored in the patient adherence database 307 of the SP system 300.

It should be noted that, in accordance with one embodiment of thepresent invention, a prescription and drug fill (which is a type ofpatient medication history data—e.g., the date on which a prescriptionwas filled by a patient) must qualify for calculating patient adherencefor a given patient and substance in order to be used by the SP modulewhen determining patient adherence data. A prescription qualifies if theprescription matches the target drug by name, has a stop date that isafter the compliance interval start date, and is either the most recentmatching prescription or has a stop date that is within N days (e.g. 30)of the start date of the next most recent prescription. A drug fillqualifies if it matches the target drug by name, has a fill date that isafter the compliance interval start date, and has a fill date that isbetween the start and stop date of a qualifying prescription. Thecompliance interval start date is the start of a compliance interval ofinterest.

Generally, patient adherence data comprises information relating to apatient's adherence, compliance, and/or persistency to prescriptionsissued to the patient. As noted above, the prescriptions may, but do notnecessarily have to be for the target drug of a cohort. For example, thepatient adherence data may comprise information relating to thepatient's first fill compliance of a prescription, the patient's firstfill interval of a prescription, the patient's compliance interval of aprescription, and any other information relating to the patient'sadhere, compliance, or persistency to a prescription.

For further example, in one embodiment of the present invention, patientadherence data comprises first fill compliance (FFC) data and patientMedication Persistency Rate (MPR) data. Generally, FFC data comprisesinformation relating to whether or not the patient has been prescribed aparticular prescribed substance (e.g., the target drug) in the pastand/or whether the patient picked-up or took the particular prescribedsubstance (e.g., the target drug) in the past.

Further, in one embodiment of the present invention, FFC data of aprescription has three possible values: (1) present; (2) absent: or (3)unknown. The FFC data has a value of present if there exists aqualifying drug fill where: (1) the fill date of the prescription isafter the start date of the prescription; and (2) the fill date of theprescription is before the end of the end of the first fill interval ofthe prescription. In such instances, the prescription was filled by thepatient after the prescription was written by the health care provider101, but before the end of the first fill interval of the prescription.Therefore, the prescription is first fill compliant.

The FFC data has a value of unknown if the start date of theprescription is after the end of the first fill interval of theprescription. In such instances, the prescription occurred after thefirst fill interval and therefore may be a refill of the prescription.Thus, information relating to a refill of a prescription does notindicate whether the patient was compliant with filling theirprescription on the first fill. In all other instances, the FFC data hasa value of absent.

Generally, MPR data comprises information relating to the patient'sadherence to a particular prescribed substance (e.g., the target drug).For example, MPR data may comprise information relating to the degree orextent of conformity of the patient to the recommendations aboutday-to-day treatment by the health care provider 101 with respect to thetiming, dosage, and/or frequency of a particular prescribed substance(e.g., the target drug), information relating to the extent to which apatient acts in accordance with the prescribed interval and dose of adosing regimen of the particular prescribed substance (e.g., the targetdrug), and information relating to the continuation the treatment by thepatient for the prescribed duration of the particular prescribedsubstance (e.g., the target drug). Therefore, in one embodiment of thepresent invention, the MPR data comprises, as a percentage, informationrelating to how often the patient filled a prescription compared withhow often s/he could have filled it optimally. Finally, it should benoted that in some embodiments of the present invention, MPR data may bereferred to as medication possession ratio data.

According to one embodiment of the present invention if there are fewerthan three qualifying fills of a particular prescription, then the MPRdata for that prescription has a value of unknown. Otherwise, if thereare three or more qualifying fills of a particular prescription, thenthe MPR data is calculated as follows. First, the patient adherencegeneration module 306 of the SP system 300 calculates complianceinterval days for the prescription. Compliance interval days is thenumber of days in a compliance interval, or the number of days that asupply of prescription is available to the patient during the complianceinterval. For each qualifying prescription, the patient adherencegeneration module 306 determines the adjusted prescription start date(the later of the start date of the prescription and the complianceinterval start date), the adjusted prescription stop date (the earlierof the prescription stop date or the current date), and the complianceinterval clays of the prescription (the adjusted stop date minus theadjusted start date).

Next, the patient adherence generation module 306 calculates the totalfill days of the prescription. Total fill days is a measure of thenumber of days that a supply of a prescription is actually filled by thepatient during the compliance interval. For each qualifyingprescription, the patient adherence generation module 306 calculates theadjusted fill start date (the later of the fill date of the prescriptionand the compliance interval start date of the prescription) and theadjusted fill stop date (the earlier of the fill date plus the fill daysand the current date). Next, the patient adherence generation module 306calculates the total fill days of the prescription (the adjusted fillstop date minus the adjust fill start date). Finally, the patientadherence generation module 306 calculates the MPR data for theprescription (the total fill days divided by the compliance intervaldays—multiplied by 100 to show as percentage).

After the patient adherence data is generated by the patient adherencegeneration module 306, the patient adherence generation module 306transmits the patient adherence data to the central portion 301 of theSP module so that the SP module may parse and analyze the patientadherence data by cohort to determine the effectiveness of a pluralityof different permutations of supplemental programs on patient adherence.

Referring to FIGS. 37a -37 b, a flow chart of a method of parsingpatient adherence data into data grouping based on a plurality ofdifferent cohorts according to an embodiment of the present invention isillustrated. The method 3700 begins when the SP module receives patientadherence data relating to a plurality of electronic prescriptions,thereby completing step 3701. It should be noted that the SP module mayreceive patient adherence data on a periodic basis (e.g., once a day),or the SP module may receive patient adherence data on a continuousbasis. Further, the patient adherence data may relate to prescriptionsthat were associated with a particular cohort or not. As discussed inmore detail below, the SP module parses the patient adherence data onthe basis of cohort to determine the effectiveness of the permutation ofsupplemental programs of each cohort.

After receiving patient adherence data, the SP module processes the dataand extracts the provider's NPI number and prescribed substance namefrom the electronic prescription associated with the patient adherencedata, thereby completing step 3702 and 3703. It should be noted that thepatient adherence data comprises information that relates to acorresponding electronic prescription processed by the EP module, and istherefore stored within the record database 304 of the SP system 300. Asa result, the SP module can extract the provider's NPI number andsubstance name from the underlying electronic prescription associatedwith the patient adherence data.

After extracting the provider's NPI number and substance name, the SPmodule determines whether the health care provider 101 identified by theNPI number is associated or part of a cohort, thereby completingdecision step 3704. According to one embodiment of the presentinvention, the determination is made by the SP module by across-referencing of the cohort relation table discussed above. In suchinstances, the SP module may cross-reference the provider's NPI numberwith the cohort relation table to determine whether the provider is partof a cohort. If the provider 101 identified by the NPI number is notassociated with a cohort, then the method returns to step 3702 and theSP module processes patient adherence data relating to anotherprescription. However, if the provider 101 identified by the NPI numberis associated with a cohort, then the method continues to decision step3705.

At decision step 3705, the SP module determines whether the prescribedsubstance identified by the electronic prescription is associated withone of the provider's cohort(s) identified in step 3704. Similar toabove and according to one embodiment of the present invention, thedetermination is made by the SP module by a cross-referencing of thecohort relation table discussed above. In such instances, the SP modulemay cross-reference the prescribed substance name with the cohortrelation table to determine whether the prescribed substance isassociated with one of the provider's cohort(s) identified in step 3704.If the prescribed substance name does not correspond with the prescribedsubstance of one of the provider's cohort(s), then the method returns tostep 3702 and the SP module processes patient adherence data relating toanother prescription. However, if the prescribed substance name doescorrespond with the provider's cohort, then the method continues to step3706.

It should be noted that in such instances, the patient adherence datarelates to an electronic prescription that meets all the cohort rules ofthe provider's cohort. However, at decision step 3706, the SP moduledetermines whether the electronic prescription caused the permutation ofsupplemental programs of the provider's cohort were activated by the SPmodule. Stated another way, the SP module determines whether the cohortrules were met by the electronic prescription and whether the currentcounter was at or below the maximum counter when the SP module processedthe electronic prescription when determining if the permutations ofsupplemental programs for the cohort would be activated.

In one embodiment of the present invention, when a permutation ofsupplemental programs of a cohort is activated for a prescription, theSP module tags the corresponding prescription. The correspondingprescription, the permutation of supplemental programs, and the tag areall stored in correlation with each other in the records database 304 orother databases of the SP system 300. Thereafter, the SP module uses thetag to determine whether the permutation of supplemental programs of acohort was activated for an electronic prescription. For example, whenreceiving patient adherence data, SP module cross-references the recordsdatabase 304 to see if the appropriate tag is associated with thecorresponding prescription, thereby indicating that the permutation ofsupplemental programs was activated. Nonetheless, the invention is notso limited, and in alternate embodiments of the present invention, thepatient adherence generation module 306 may determine whether thepermutation of supplemental programs was activated for a particularprescription using other methods.

Next, after the SP module determines that the electronic prescriptioncaused the permutation of supplemental programs of the provider's cohortto be activated by the SP module, the SP module associates the patientadherence data with the corresponding cohort of the health care provider101, thereby completing step 3707. Thereafter, the SP module stores thepatient adherence data in association with the health care provider'scohort in the cohort database 305, thereby completing step 3708.

Next, at decision step 3709, the SP module determines whether all of thereceived patient adherence data for all the prescriptions has beenparsed by cohort. If so, then the process ends at step 3711. However, ifthere remains patient adherence data that has not been parsed by the SPmodule, then the Method 3700 continues to step 3710, and as such,returns to step 3702 discussed above.

According to one embodiment of the present invention, more than oneprescription of a patient may be combined in order to determinecompliance data. Thus, if a patient has more than one prescription for agiven substance, it may be the case that the prescriptions should becombined for the purposes of calculating compliance data. For example,prescriptions may be combined if they are for the same patient and thesame substance, and the prescriptions have overlapping prescriptiondates. For example, if prescription 1 has a start date of Mar. 1, 2011and stop date of Jun. 1, 2011 and prescription 2 has a start date of May1, 2011 and a stop date of Oct. 1, 2011, then the prescriptions may becombined and considered one prescription for the purposes of determiningpatient adherence data.

4. Analyzing the Patient Adherence Data to Determine the Effectivenessof the Different Permutations of Supplemental Programs on PatientAdherence

After parsing the patient adherence data by cohort, the SP moduleanalyzes the patient adherence data to determine the effectiveness ofeach of the different permutations of supplemental programs on patientadherence. In one embodiment of the present invention, when the currentcounter of all the cohorts of a program cohort group reach the maximumcounter, the SP module ceases to activate the permutations ofsupplemental programs for the cohorts of the program cohort group, andbegins to analyze patient adherence data to determine the effectivenessof the different permutations of the supplemental programs of a programcohort group on patient adherence. However, in other embodiments of thepresent invention, the SP module may analyze patient adherence datacontinuously in real-time, even as the SP module is also stillactivating permutations of supplemental programs for a program cohortgroup.

According to one embodiment of the present invention, one of the cohortsout of the plurality of cohorts of the program cohort group is a controlgroup. Since the control group either does not comprise any associatedsupplemental programs (i.e., the permutation of supplemental programs ofthe control group is empty) or the control group comprises one or moresupplemental programs that are also associated with every one of theother cohorts of the program cohort group, then the control group can beused as a basis of comparison to determine the effectiveness of thesupplemental programs of the other cohorts of the program cohort group.Stated more simply, the SP module may determine the effectiveness of thepermutations of supplemental programs by using the control group as abaseline indicator of standard patient adherence to the target drug.

In embodiments that do not comprise a control group, the basis ofcomparison may be the average patient adherence for the target drug ingeneral. This may be determined by the SP module in many ways, includingbut not limited to, the patient adherence data for the target drug thatis stored within the patient adherence database 307 and was generated bythe patient adherence generation module 306. Further, in otherembodiments that do not comprise a control group, the different cohortsmay be simply compared to one another, with the assumption that thepermutations of supplemental programs have a beneficial effect onpatient adherence. After determining a basis of comparison (e.g., thecontrol group), the SP module will analyze the patient adherence data ofeach cohort of a program cohort group to determine the effectiveness ofeach of the different permutations of supplemental programs on patientadherence.

In one embodiment of the present invention, the SP module determines theeffectiveness using one or more algorithms that are configured tocompare multiple sets of data to one another. According to oneembodiment of the present invention, the algorithms are stored withinthe cohort database 305. The data that is compared to determine theeffectiveness of the permutations of supplemental programs on patientadherence includes, but is not limited to, patient adherence data,coupon redemption data, and patient feedback data.

After the data is compared using the one or more algorithms, the SPmodule may display effectiveness data on a display device to anadministrator of the SP system 300. This allows the administrator of theSP system 300 to visually interpret which permutation of supplementalprograms was most effective for encouraging patient adherence to thetarget drug. As discussed in more detail below, the effectiveness datamay be displayed in graphical representations or in numerical values.

Referring to FIG. 38a , a graphical representation of the effectivenessof different permutations of supplemental programs on patient's firstfill compliance according to one embodiment of the present invention isillustrated. For example, in one embodiment of the present invention,the SP module determines the effectiveness of the permutations ofsupplemental programs by comparing the first fill compliance data of theprescriptions of a cohort to the other cohorts of the program cohortgroup. It should be noted that first fill compliance (FFC) dataindicates whether the patient filled the medication promptly afterreceiving the prescription. Further, in embodiments where one of thecohorts out of the plurality of cohorts is a control cohort, the SPmodule will compare the FFC data of the prescriptions of each cohortwith the control cohort in order to determine the effectiveness of thesupplemental programs of each cohort. The permutation of supplementalprograms of the cohort whose prescriptions have the highest FFC datawill be considered the most effective on patient adherence. This isbecause the patients receiving that permutation of supplemental programsof that cohort were more likely to comply with the first fill of theprescription, and this increase in adherence is determined to be duefrom the supplemental programs those patients received.

Referring to FIG. 38b , a graphical representation of the effectivenessof different permutations of supplemental programs on patient'smedication persistency rate displayed on a display device according toone embodiment of the present invention is illustrated. For furtherexample, in one embodiment of the present invention, the SP moduledetermines the effectiveness of the permutations of supplementalprograms by comparing the patient Medication Persistency Rate (MPR) dataof the prescriptions of a cohort to the other cohorts of the programcohort group. It should be noted that MPR data is a percentile (from0-100%) that indicates how often a patient filled a medication comparedwith how often s/he could have done so. Specifically, in embodimentswhere one of the cohorts out of the plurality of cohorts is a controlcohort, the SP module will compare the MPR data of the prescriptions ofeach cohort with the control cohort in order to determine theeffectiveness of the supplemental programs of each cohort. Thepermutation of supplemental programs of the cohort whose prescriptionshave the highest MPR data will be considered the most effective onpatient adherence. This is because the patients receiving, thatpermutation of supplemental programs of that cohort were more likely tofill their prescription when having the opportunity.

Specifically, referring to FIGS. 38a and 38b concurrently, cohort number1 is the control cohort, while cohort numbers 2-6 are other cohorts ofthe program cohort group that were each assigned a different permutationof supplemental programs to measure the effectiveness of those programson patient adherence. It should be noted that cohort number 1 was notassigned any supplemental programs (i.e., its permutation ofsupplemental programs is empty). Further, the program control group isprogram control group 8, and the target drug is Lipitor®. As illustratedin FIG. 38a , cohort number 1, which was the control group, has a FFC of60%. This means that 60% of the prescriptions that were written by thehealth care providers 101 of cohort 1 for the target drug were filledwithin the first fill interval of the prescription. Further, asillustrated in FIG. 38b , cohort number 1, which was the control group,has a MPR of 45%. This means that, on average, the patients who wereprescribed the target drug by the health care providers 101 of cohort 1had an MPR of 45%. Cohort number 1's FFC of 60% and MPR of 45% may beused as a baseline to determine the effectiveness of the otherpermutations of supplemental programs were assigned to the othercohorts.

As noted above, FIGS. 38a and 38b are two examples of graphicalrepresentations of the effectiveness of different permutations ofsupplemental programs on patient adherence. As exemplified in FIG. 38a ,cohort number 5 has the highest FFC rate of 90%, and therefore, thepermutation of supplemental programs assigned to cohort number 5 is themost effective at increasing patient's first fill compliance to thetarget drug. By contrast, cohort number 2 has the lowest FFC rate of thenon-control cohorts of 63%, and therefore, the permutation sosupplemental programs assigned to cohort number 2 is the least effectivein increasing patient's first fill compliance to the target drug.Moreover, as exemplified in FIG. 38b , cohort number 4 exemplifies thehighest MPR of 81%, and therefore, the permutation of supplementalprograms assigned to cohort number 4 is the most effective at increasinga patient's persistence to the target drug regimen. By contrast, cohortnumber 3 exemplifies the lowest MPR rate of the non-control cohorts of58%, and therefore, the permutation of supplemental programs assigned tocohort number 3 is the least effective at increasing a patient'spersistence to the target drug regimen. Thus, as illustrated, dependingon the means of measurement of patient adherence (FFC, MPR, etc.),different permutations of supplemental programs may be most effective.As a result, by using cohorts to test the effectiveness of supplementalprograms on a variety of different measurements of patient adherence,the SP module may be used to determine the most effective combination ofsupplemental programs to increase patient adherence in the most desiredmanner.

However, it should be noted that the invention is not so limited, and inother embodiments of the present invention, the SP module determines theeffectiveness of the permutations of supplemental programs by comparingone or more forms of patient adherence data of the prescriptions of theplurality of cohorts of the program cohort group. Stated another way,the invention is not limited to comparing FFC data and MPR data whendetermining the effectiveness of the plurality of cohorts of a programcohort group. Any patient adherence data may be used by the SP module.Finally, it should be noted that the graphic representation exemplifiedin FIGS. 38a and 38b may be displayed on a display device of theadministrator of the SP system 300, to a pharmaceutical company, or toany other person or system of the system 1000.

For even further example, in another embodiment of the presentinvention, every cohort of a program cohort group, including a controlcohort comprises a supplemental program that distributes a coupon forthe target drug to the patient upon activation. In such instances, thenon-control cohorts of the program cohort group all comprise differentsupplemental programs in addition to the supplemental program thatdistributes a coupon. As a result, the SP module measures theeffectiveness of each permutation of supplemental programs by comparingthe rates of coupon redemption of the prescriptions of each cohort ofthe program cohort group. Therefore, the patients who are receiving thepermutation of supplemental programs of the cohort with the highesteffectiveness on patient adherence will have redeemed their coupon moreoften that the patients receiving the permutations of supplementalprograms of the other cohorts.

According to one embodiment of the present invention, after determiningthe effectiveness of the supplemental programs on patient adherence, theSP module generates patient adherence reports based on the determinedeffectiveness. After generation of the reports, the SP module maildeliver the reports to any one of the administrators of the SP system300, any other system or module of the system 1000, or a particularpharmaceutical company. Examples of graphical reports are exemplified inFIGS. 38a and 38b . Nonetheless, it should be noted that the inventionis not limited to any specific type or format or graphical report.Further, in alternate embodiments of the present invention, the patientadherence data of each cohort may be displayed purely as numericalvalue, as numerical values and graphical representations, or justgraphical representations.

After the graphical report is generated by the SP module, the graphicalreport is saved to the cohort database 305 of the SP system 300.Further, according to one embodiment of the present invention, thecohort relation table is updated with the graphical report stored inassociation with the associated health care provider 101 and cohort ofthe graphical report.

While the embodiment of the present invention has been described withreference to the accompanying drawings, it can be understood by thoseskilled in the art that the present invention can be embodied in otherspecific forms without departing from its spirit or essentialcharacteristics. Therefore, the foregoing embodiments and advantages aremerely exemplary and are not to be construed as limiting the presentinvention. The present teaching can be readily applied to other types ofapparatuses. The description of the foregoing embodiments is intended tobe illustrative, and not to limit the scope of the claims. Manyalternatives, modifications, and variations will be apparent to thoseskilled in the art. In the claims, means-plus-function clauses areintended to cover the structures described herein as performing therecited function and not only structural equivalents but also equivalentstructures.

1. A method comprising: generating a first user interface for receivingan electronic prescription for a patient from a health care provider;receiving, via the first user interface, the electronic prescription fora prescribed substance; and responsive to receiving the electronicprescription: obtaining adherence data for the patient, identifying,from a database of supplemental programs, supplemental programsassociated with the prescribed substance, the identified supplementalprograms being associated with at least one rule relating to adherencedata that is met by the adherence data for the patient, responsive toidentifying the supplemental programs, generating a second userinterface that presents the supplemental programs for selection by thehealth care provider, and responsive to receiving selection of at leastone of the supplemental programs in the second user interface, providingthe supplemental programs to the patient.
 2. The method of claim 1,wherein the supplemental programs are in a cohort of a program cohortgroup, the program cohort group being for the prescribed substance andthe cohort being a cohort in the program cohort group that has a highestadherence score of cohorts in the program cohort group.
 3. The method ofclaim 2, wherein the at least one rule is associated with the programcohort group.
 4. The method of claim 1, wherein the at least one rulerelates to a persistency range and the adherence data includes apersistency rate for the patient that is compared with the persistencyrange.
 5. The method of claim 1, wherein the at least one rule relatesto a minimum persistency rate and the adherence data includes apersistency rate for the patient that is compared against the minimumpersistency rate.
 6. The method of claim 1, wherein the at least onerule relates to a first fill compliance rate and the adherence data forthe patient includes a first fill rate for the patient that is comparedagainst the first fill compliance rate.
 7. The method of claim 1,wherein the database of supplemental programs associates one or morerules with a supplemental program, the at least one rule relating toadherence data being one of the one or more rules.
 8. The method ofclaim 7, wherein the one or more rules include: a minimum predeterminedtime period that the patient has been prescribed the prescribedsubstance; a first fill rate; a persistency rate; a patient age; adisease state; or a general adherence history.
 9. The method of claim 1,wherein the at least one rule relates to an adherence ratio range withrespect to the prescribed substance, wherein a patient meets the atleast one rule when a historical adherence ratio for the patient withrespect to the prescribed substance falls within the adherence ratiorange.
 10. The method of claim 1, wherein the adherence data for thepatient is collected from a payor and/or a pharmacy system.
 11. Themethod of claim 1, wherein providing the supplemental programs includes:retrieving, from one or more databases, a first set of delivery modesthat are available for the patient associated with the electronicprescription; retrieving, from the one or more databases, a second setof delivery modes that are associated with each supplemental program;comparing the first set of delivery modes and the second set of deliverymodes to identify a list of common delivery modes that are available forthe patient and associated with one or more supplemental programs; andpresenting the one or more supplemental programs with the list of commondelivery modes for selection and acceptance.
 12. The method of claim 1,wherein the adherence data for the patient includes data from which todetermine: for each prescription of one or more prescriptions: a numberof refills for the prescription; a prescription start date for theprescription; a prescription stop date for the prescription; informationrelating to whether the patient picked up the prescription, a number ofrefills that the patient filled for the prescription, and a time framebetween refills in comparison to a duration of the prescription.
 13. Asystem comprising: at least one processor; and memory storinginstructions that, when executed by the at least one processor, causethe system to provide a user interface configured to: receive anelectronic prescription of a prescribed substance for a patient from ahealth care provider; display a persistency rate for the patient,determine that the persistency rate for the patient satisfies a rulerelating to adherence data; and responsive to determining that thepersistency rate for the patient satisfies the rule: presentsupplemental programs for selection by the health care provider, thesupplemental programs being associated with the prescribed substance ina database of supplemental programs, and responsive to receivingselection of at least one of the supplemental programs, providing the atleast one selected supplemental program to the patient.
 14. The systemof claim 13, wherein the persistency rate includes a persistency ratefor the prescribed substance and a persistency rate for the patient thatincludes any previously prescribed substance.
 15. The system of claim14, wherein the rule includes a minimum persistency rate and the rule issatisfied when the persistency rate for the prescribed substance fallsbelow the minimum persistency rate or when the persistency rate for thepatient falls below the minimum persistency rate.
 16. The system ofclaim 13, wherein the persistency rate includes a persistency rate forthe prescribed substance and the rule includes a range and the rule issatisfied when the persistency rate for the prescribed substance fallswithin the range.
 17. The system of claim 13, wherein the persistencyrate includes a persistency rate for the patient that includes anypreviously prescribed substances and the rule includes a range and therule is satisfied when the persistency rate for the patient falls withinthe range.
 18. The system of claim 13, wherein the persistency rate isobtained at least partially using data from one or more pharmacy systemsor one or more payor systems.
 19. The system of claim 13, wherein theuser interface is further configured to: display, for the at least onesupplemental program selected, at least two delivery modes; and receiveselection of a delivery mode of the at least two delivery modes, whereinproviding the at least one selected supplemental program is performedusing the selected delivery mode.
 20. The system of claim 13, whereinthe supplemental programs are in a cohort of a program cohort group, theprogram cohort group being for the prescribed substance and the cohortbeing a cohort in the program cohort group that has a highest adherencescore of cohorts in the program cohort group.